Enforce consistency across Automation Workflow Policy definitions

There is a lack of consistency across Policies when defining Automation workflows. For example, when creating a Database policy, there are four categories of workflow: 

1. Cloud DB scale (no toggle)
2. Database suspend actions
3. Database reconfiguration actions (there is no Edit option here - the help text should explain that Actions will be Recommend only & cannot be scheduled)
4. Database deletion actions

For the last three, you enable/disable the actions using a top-level toggle button (DB top-level.png). When you edit any of the settings with a toggle, you're shown the "On generation" option "Do not generate actions" (DB suspend.png). This is inconsistent across Policy types. For example, for Database Server Policy, you have:

1. Database Server scaling actions
   1. Disruptive irreversible scaling
   2. Disruptive reversible scaling
   3. Non disruptive reversible scaling
   4. Non disruptive irreversible scaling

When you turn off the toggle on #1, all of the subordinate settings are disabled, and you don't have the option to set "On generation" for any of the subordinate action types to "Do not generate" (DB Server actions.png). It's all or nothing. 

This behavior prevents users from suppressing action generation for only some of these action types. If the user NEVER wants to take, for example, Disruptive irreverisble scaling actions they don't have the option to suppress the generation of ONLY that action type. This could lead to artificially inflated "Potential Savings" by having Turbo generate actions that will never be taken.

So, this Idea is to standardize the Automation workflow settings for ALL Policies (not just the ones referenced here) to act as follows:

• Always use the toggle to allow users to enable/disable an action category
• Always provide the option Do not generate for On generation so that users have the flexibility to disable action generation at the most granular level
• Enhance descriptive text to better inform the user about what the action setting does
• Add help text (the "circled i") for each action type to provide easily accessible comprehensive in-application documentation