Create and register page types for the new RBAC endpoints

[jbradberry]

SUMMARY

Some new endpoints are being exposed, and old endpoints are now marked as deprecated. Update awxkit in order to properly support the new way in the cli, but also so that QE testing can start making use of the new stuff.

ISSUE TYPE

• Bug, Docs Fix or other nominal change

COMPONENT NAME

• API

[jbradberry]

cc @AlanCoding @fosterseth

[jbradberry]

I hope and think that this should be as easy as:

• Create new Page types corresponding to the new endpoints (I did this in the first commit) and register them
• Confirm that an OPTIONS call against the new endpoints gives sane info about postable fields
• Include @AlanCoding 's new RBAC endpoints in the list of things that get exported
• Make sure exports of top-level things don't break if the top-level list endpoint doesn't exist (allowing this code to be used with both old-style and new-style)
• Make sure the export detects existence of new style endpoints and ignores the old style endpoints in that case
• Detect on import side if old-style or new-style export structure is being passed in, and hit the appropriate endpoints corresponding to that
• Make sure that the new endpoints are in the right place in the awxkit dependency hierarchy

[AlanCoding]

resources.role_definition_team_assignments would be read-only, so it looks like the most correct thing would be to delete it here.

[AlanCoding]

The other thing worth noting is that assignments are immutable, meaning the detail endpoint, resources.role_user_assignment, would not allow PATCH/PUT... but it seems that no references to the detail endpoint exist here in the first place, so I guess we're good.

[AlanCoding]

thanks! this is a good step forward.

• left one minor request that the sublist shouldn't map POST to anything
• delete comments with imports of HasCopy and the like.