[#7024] Platform: Fixed edit number of nodes in AZ section

[gaurav061]

Description: The user was not able to edit the numbers of nodes from the AZ section while editing the universe.

[gaurav061]

Fix: currentPlacementStatus prop was null initially when we land to edit universe page, so in mounting lifecycle i fetched this info if it is undefined or null.
Please add your comments

[lgtm-com]

This pull request introduces 1 alert when merging 9b4f091 into 84ebc32 - view on LGTM.com

new alerts:

• 1 for Unused variable, import, function or class

[lgtm-com]

This pull request introduces 1 alert when merging 6f363e9 into 84ebc32 - view on LGTM.com

new alerts:

• 1 for Unused variable, import, function or class

[sshev]

Before ad3a72a commit the currentPlacementStatus prop was filled here

yugabyte-db/managed/ui/src/components/universes/UniverseForm/AZSelectorTable.js

Line 469 in 0857a10

this.props.setPlacementStatus(placementStatusObject);

Now this never happens due to extra conditions added at ClusterFields component:
{placementStatusOnprem || regionAndProviderDefined && azSelectorTable}

This seems to be the real root cause, so let's investigate in that direction pls.

[gaurav061]

After adding the above condition {placementStatusOnprem || regionAndProviderDefined && azSelectorTable}AzSelector component is being rendered with this _.isEqual(universeConfigTemplate, this.props.universe.universeConfigTemplate) as true and thus it is blocking this this.props.setPlacementStatus(placementStatusObject); So, we need this call to be made in UNSAFE_componentWillMount lifecycle for 1st time rendering for subsequent rending the call will be made from UNSAFE_componentWillReceiveProps lifecycle.
Please add to it.