Regression identified during testing of the ec2-plugin on Jenkins 2.403+.

When the clouds management page was reworked, submitting a config change to the cloud node does not return the top of the cloud page. Instead it returns to the cloud node page. This is not a problem if the name has not been changed. However, once the name has been changed, the cloud node page is now invalid and user is greeted with a 404.

Reproduction steps:

• Go to manage jenkins -> clouds
• Create a new cloud node and save
• Select config for the new cloud node
• update the name and click save