feat: Resource to manage XSUAA Api Credentials

[diya-dhan]

Purpose

fix #689

The BTP CLI supports managing API credentials for the SAP Authorization and Trust Management (XSUAA) service, enabling users to interact programmatically with REST APIs. These APIs facilitate the management of entities and user provisioning across subaccounts, global accounts, or directories.

The provider now has introduced new resources to manage these API credentials at various levels: subaccount, global account, and directory. Users can create credentials of either the certificate type (currently, certificates can only be provided as strings) or the secret type. The state file will store the client secret or certificate key information for reference when using these APIs.

Please note that updating credentials is not supported by this resource, as there is currently no API available for this purpose.

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

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

How to Test

• Test the code via automated test

go test ./...

What to Check

Verify that the following are valid:

• Automated tests are executed successfully

Checklist for reviewer

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

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

[lechnerc77]

Sonar Cloud Quality check is accepted to be below 80%

[diya-dhan]

Some minor changes requested for import documentation

General question: there are no data sources available. This is due to the fact that the returned data is only a fraction of the complete data and we leave it out?

Yes, like you mentioned the GET call does not return a lot of the information that is relevant to the user. This is only known at the time the api credentials are created. Additionally, as of now, there is no use case where the api credentials can be used in other BTP resources, due to which a datasource for it didn't really make sense.