Currently RBAC has data in v1 tables like role, binding mappings, and we need to migration in into v2 tables (bindings, v2 roles)

 
This spike is necessary to define the scope and approach for migrating existing RBAC v1 data (specifically from v1 tables like roles and binding mappings) into the newly designed v2 models and tables (such as v2 roles and role-bindings). This migration effort is a critical component of the broader initiative to establish RBAC v2 APIs and data models. 
 
The need to define the scope for this migration is why it's marked as a spike. It will involve understanding the transformation and mapping of existing v1 data structures to their v2 counterparts. This work depends on the two linked tickets as the migration depends on the finalized V2 data models and API designs. The outcome of this spike will ensure a clear upgrade path for existing v1 consumers. 
 
Goals of this Spike: * Determine and outline potential approaches for the migration process, considering factors like downtime, data volume, and reversibility.

• Lay the essential groundwork for ensuring the maintainability and resilience of the RBAC service during and after the migration.