[AMBARI-23683] dfs_ha_initial_* properties should be removed after installation

[adoroszlai]

What changes were proposed in this pull request?

Some temporary properties required for blueprint-based provisioning of NameNode HA setup may cause problems later (eg. during upgrade).

This change proposes:

1. a listener that removes these properties (eg. dfs_ha_initial_namenode_active) when blueprint-based cluster provisioning finished successfully
2. to avoid the need to restart all HDFS components, the properties need to be added to cluster-env instead of hadoop-env
3. for backward compatibility, move any such property specified in hadoop-env in the blueprint to cluster-env during provisioning

How was this patch tested?

Deployed clusters via blueprint using the following scenarios:

• NN HA with Ambari-generated properties
• NN HA with user-specified properties in hadoop-env
• single NN

Verified that the removed properties are not sent in subsequent commands (eg. service check).

[asfgit]

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1985/
Test FAILed.
Test FAILured.

[asfgit]

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1992/
Test FAILed.
Test FAILured.

[asfgit]

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1998/
Test PASSed.

[rnettleton]

Patch looks fine to me.