1. Proposed title of this feature request: Node/Machine Delete Policy
2. What is the nature and description of the request?

Customers need the ability to choose the order in which nodes are removed from nodePool when they're scaling down or updating. In OCP, MCO will remove nodes according to the age within the machine config pool. In HyperShift, nodes will be removed in random. 

3. Why does the customer need this? (List the business requirements here)

• a. Customers run OpenShift in stand-alone, Hosted Control Planes, and/or managed. Lack of consistencies across these APIs is a problem to migrate between offerings. 
• b. Customers will have specific nodes that they need to replace for compliance reasons: for e.g., all nodes older than 30 days must be replaced. If there's no path to upgrade, customers would like to use scaling down or similar methods to remove older nodes.
• c. Customers will have applications that can not handle disruptions so when scaling down happens instead of picking a node randomly, they'd want to have more control over which node to be removed. 

4. List any affected packages or components: HyperShift API

>> DeletePolicy- Ability for customers who choose either Upgrade Type to pick a Delete Policy for node during the upgrade:

I don't see support for the DeletePolicy in HyperShift: https://hypershift-docs.netlify.app/reference/api/#hypershift.openshift.io/v1beta1.ReplaceUpgrade