fix: Rbac not working for resources having long names

[prakash100198]

Description

When we set permission group for a resource with long name (length>100) the role group was not getting stored in the casbin_rules and roles table in orch database, hence RBAC was not working in that case, this pr fixes that issue.
Fixes #3078

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
This has been tested by deploying the fixed code image into my cluster having SSO configured.
Test Scenarios:-

1. Add user and assign permission to the user for that resource with the long name, now add this permission group to that user and check for that user if that kubernetes resource is visible or not.
2. Check my making different combinations of permission roles and assign to the user, and check if resource is visible or not.

Checklist:

• The title of the PR states what changed and the related issues number (used for the release note).
• Does this PR requires documentation updates?
• I've updated documentation as required by this PR.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have tested it for all user roles.
• I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information