Include ML in base privileges

[legrego]

The Machine Learning feature should be included as part of the base privileges for the 8.0 release.
This is considered a breaking change since it would grant considerable privileges to existing users, and this may not be desirable for certain installations.

Joe edit 8/17: also mention in Upgrade Assistant if some users did not have access to ML currently will now have access in 8.0.

[jportner]

As mentioned in the linked meta issue (#111160), we need to do separate things for 7.x and master:

• 7.x branch: Ensure that the 8.0 upgrade assistant accurately reflects all of the deprecations

  • Each deprecation should be set at the appropriate level (critical if it blocks the upgrade, warning if not)
  • Each deprecation should correctly describe when the breaking change will take effect (8.0, or a future version)
  • The copy (text) should be reviewed with the docs team
  • Any automation to fix the problem (correctiveActions.api registered in the DeprecationsService) should be implemented and tested

• master branch: Ensure that, for breaking changes that take effect in 8.0, all appropriate code is removed

We discussed this particular issue with Platform leadership, and decided that the upgrade assistant in 7.x should provide a warning for any custom roles that do not currently grant access to ML that will grant access to ML post-8.0.
This means any role that grants a base privilege (all or read).

We should just surface a warning, we do not need to add any automated remediation to change any roles.

[jportner]

We should just surface a warning, we do not need to add any automated remediation to change any roles.

One additional point: ML is only available for Platinum+ licenses, so we should only surface this warning for clusters >= that license level.