Move role creation into the recipe instead of feature activation

[MikeAlhayek]

Fix #12425

@jtkech please check this out when your time permits since we chatted about this in the issue.

Here is a summary of the enhancements this PR brings

1. We can now use recipe step to explicitly list the roles we want to use for the site. We are no longer forced to use the default roles.
2. If a role is deleted, it wont come back at some point after installing new features. Currently, even if we delete a role, it could come back after installing more features.
3. If the Roles feature is disabled, and re-enabled later, we keep track of permissions history to automatically assign any permission that would not have been assigned previously while the Roles feature is disabled.
4. If an enabled feature introduces new permissions, it'll now get assigned to the proper roles by default "if these roles exists".

[MikeAlhayek]

@sebastienros this is ready for a quick review.

[gvkries]

This PR breaks the permissions feature. Manually removed permissions are added back when the site restarts.

[MikeAlhayek]

@gvkries please open a new issue with steps to reproduce the issue. You can reference this PR in the new issue.

[hyzx86]

@MikeAlhayek here: #13024