fix(permissions): alpha role has all full features

[dpgaspar]

SUMMARY

Currently Alpha role does not include the "Manage" menu and it's sub items. But user's still have underlying access to the ModelView's that are included on the "Manager" menu. This PR proposes adding "Manage" menu and their sub items to the "Alpha" Role, making it an "All features included" role, except for security and SQLLab.

ADDITIONAL INFORMATION

• Has associated issue:
• Changes UI
• Requires DB Migration.
• Confirm DB Migration upgrade and downgrade tested.
• Introduces new feature or API
• Removes existing feature or API

[mistercrunch]

By adding the MVs in ADMIN_ONLY_VIEW_MENUS you're removing access to Alpha and Gamma. I don't think that's what we want

[dpgaspar]

That was my objective, since by removing the "Manage" menu item, it's kind of implied the user does not have access to the AnnotationsLayerModelView, CssTemplateModelView, QueryView but he does.

But seems like we are using the old API for the annotations. Would be awesome to instead of removing we would add the "Manager" menu item to Alpha, that would make it more consistent, and inline with the idea that an Alpha user has access to all features except security

[mistercrunch]

I think users still access the API in some other ways though (dashboard / explore / SQL Lab), we'd have to check/confirm whether they hit the modelview endpoints or not.

[dpgaspar]

@mistercrunch , I've reverted the direction here. I'm adding the Manage menu and it's subitems to the alpha role. What do you think?

[mistercrunch]

+1 on a unit test, do we have a doc somewhere that give an idea of what Gamma is? Also should have a notice pointing to this PR in UPDATING.md

[dpgaspar]

Good points, I'll add both. I think we don't have a doc describing what roles are, I'll create one on the docs if it does not exist

[villebro]

I agree with the scope of Alpha permissions. This also needs a rebase.