fix: role collection name handling

[lechnerc77]

Purpose

• Change the handling addresses for the import. As no naming conventions or constraints are in place we switch to generic resource addresses for the import
• This PR transfers all import provider to this logic
• closes [BUG] Exporter uses role collection name as resource name #189

Does this introduce a breaking change?

[X] Yes - Output of names in JSON changes
[ ] No

Pull Request Type

What kind of change does this Pull Request introduce?

[X] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Test the code via automated test

make test

What to Check

Verify that the following are valid:

• Automated tests are executed successfully

Other Information

Although the readability suffers this change will keep our functionality working independent of any SAP internal or customer specific naming conventions
As it is consistent for all resources this approach was chosen instead of replacements that are likely cot covering 100% of the cases.

Checklist for reviewer

The following organizational tasks must be completed before merging this PR:

• The PR is assigned to the Project board and a status is set (typically "in review").
• The PR has the matching labels assigned to it.
• The PR has a milestone assigned to it.
• If the PR closes an issue, the issue is referenced.
• Possible follow-up issues are created and linked.

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[CHERIANS]

LGTM