Hand the authorization layer off to dojo-pro. OS keeps a legacy
``is_superuser`` / ``is_staff`` / ``authorized_users`` model and the
seven RBAC + Dojo_Group classes survive as ``managed=False`` shells in
``dojo/authorization/models.py`` so historical pro migrations
(``pro.0001_plugiun_consolidation`` ``EnhancedDojoGroup.group``,
``pro.0034_pghistory_for_permissions_models`` proxy bases) keep
resolving when Django reloads project state. OS code makes no
runtime references to Pro.

Single ``dojo.0268_release_authorization_to_pro`` migration folds:
- Re-introduces ``authorized_users`` M2M on Product / Product_Type and
  backfills it from the RBAC tables (Member / Group → flat membership;
  Global_Role(Owner|Writer|Maintainer|API_Importer) → ``is_superuser`` /
  ``is_staff``).
- Drops the redundant post-RBAC ``members`` / ``authorization_groups``
  M2M accessors on Product / Product_Type (the through-tables remain).
- Flips the eight authorization shells to ``managed=False`` and pins
  their ``db_table``s.
- ``RemoveField``s ``default_group`` / ``default_group_role`` /
  ``default_group_email_pattern`` from ``dojo_system_settings`` (Pro
  copies the values onto ``EnhancedSystemSettings`` first via
  ``run_before``).

Plus the Tailwind UI rebuild and the OS surface tidying that this
branch was already carrying.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>