refactor(user_roles): implement parent group info based role APIs

[kanikabansal-juspay]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

POST /user/role/v2

• Creates a role using parent_groups (with name + scopes) instead of granular groups.
• Internally maps parent_groups + scopes to existing granular permissions for DB storage.

GET /user/role/list/?entity_type={entity_type}&groups=true

• Replicates existing /user/role/list functionality but replaces the groups field with a parent_groups array containing:
  • name
  • description
  • scopes

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

We are standardizing all role-related APIs (/role/list, /role/v2) to use parent group + scopes rather than granular permissions like we use in the Invite api.

Improves readability for FE consumers and ensures consistency across role creation and retrieval.

How did you test it?

1. Create Custom Role
   Request:

curl --location 'http://localhost:8080/user/role/v2' \
--header 'Cookie: *******
--header 'Content-Type: application/json' \
--data '{
    "role_scope": "merchant",
    "parent_groups": [
         {
            "name": "Operations",
            "scopes": [
                "read",
                "write"
            ]
        },
        {
            "name": "Connectors",
            "scopes": [
                "write"
            ]
        },
        {
            "name": "Analytics",
            "scopes": [
                "read"
               
            ]
        },
        {
            "name": "Internal",
            "scopes": [
                "read",
                "write"
               
            ]
        }

    ],
    "role_name": "roles_123"
}'

2. Get Role Info List

curl --location 'http://localhost:8080/user/role/list/?entity_type=merchant&groups=true' \
--header 'Cookie: *******

Response:

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
crates/router/src/routes/app.rs	97% smaller
crates/router/src/core/user_role.rs	96% smaller
crates/common_enums/src/enums.rs	93% smaller
crates/api_models/src/events/user_role.rs	62% smaller
crates/router/src/services/authorization/permission_groups.rs	47% smaller
crates/router/src/routes/lock_utils.rs	36% smaller
crates/router/src/core/user_role/role.rs	33% smaller
crates/router/src/routes/user_role.rs	13% smaller
crates/api_models/src/user_role/role.rs	7% smaller
crates/router_env/src/logger/types.rs	0% smaller