[AAP-70261] Fix role user assignment

[nickbhasin]

Description

• What is being changed?
  The hardcoded role name check is being replaced with a dynamic API endpoint mapping derived directly from the role definition's content_type attribute.
• Why is this change needed?
  The module previously failed to assign custom roles that didn't start with specific prefixes.
• How does this change address the issue?
  It correctly extracts the base object type from the content_type string (e.g., mapping shared.organization to organizations) to ensure the API request routes to the correct destination regardless of the role's name.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Test update
• Refactoring (no functional changes)
• Development environment change
• Configuration change

Self-Review Checklist

• I have performed a self-review of my code
• I have added relevant comments to complex code sections
• I have updated documentation where needed
• I have considered the security impact of these changes
• I have considered performance implications
• I have thought about error handling and edge cases
• I have tested the changes in my local environment

Testing Instructions

Prerequisites

Steps to Test

Expected Results

Additional Context

Required Actions

• Requires documentation updates
• Requires downstream repository changes
• Requires infrastructure/deployment changes
• Requires coordination with other teams
• Blocked by PR/MR: #XXX

Screenshots/Logs

[rohitthakur2590]

lets also fix this in 2.7 .

[github-actions]

DVCS PR Check Results:

PR appears valid (JIRA key(s) found)

[nickbhasin]

lets also fix this in 2.7 .
its working in 2.7