Description of problem:

Do not enable "Save" button ( it could be disabled) when  there is no definition change in "Edit machine pools" dialog. It is not a good usability experience and only when there is a change in existing definition, then enable "Save" button. This also sends a patch request to backend resulting machine pool update (without any change).
See attached recording SAvebuttonEnabledNoDefinitionChange.mp4

How reproducible:

 Always

Steps to reproduce:

1. Launch OCM UI staging.
2. Select a ROSA /OSD cluster.
3. Click on "Edit machine pools" option from the context menu.
4. See the behavior of save button.

Actual results:

Save button always enabled allowed user to click the save button without any definition change.

Expected results:
Do not enable "Save" button ( it could be disabled) when  there is no definition change in "Edit machine pools" dialog