implement proper handling of appName for apps

[rui1610]

Purpose

This PR implements a proper handling of app subscriptions that have an appName that differs from the commercialAppName.

Does the PR solve an issue

[ ] Yes - Please add issue number
[x] No

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

[x] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Add the app subscription for "integrationsuite". Without this PR the btp-setup-automator won't find the respective app subscription in your sub account, as the appName differs from the commercialAppName.

What to Check

Verify that the following are valid

• The app subsucription works for integrationsuite

Other Information

Once "slim" integration test is done, I'll request a review for the updated code.

[rui1610]

"Slim" integration test ran through without any issues (https://github.com/SAP-samples/btp-setup-automator/actions/runs/4367592247).

I've just started as well the "full" integration test (https://github.com/SAP-samples/btp-setup-automator/actions/runs/4367881386), to see whether there are other cross-dependencies I've overlooked with this PR.

[lechnerc77]

To be discussed, not approved