[ACA-5022] Configure SonarCloud phase2

[brahmanim]

SUMMARY
Resolves ACA-5022

Reported CI Issues
Integration tests #184

[brahmanim]

SonarCloud coverage tests for running integration tests are working.
I have checked this workflow, with workflow_run that always runs, and changed to workflow_call, to avoid the security issue of Make sure that no untrusted code is executed from a fork.
There are Multiple integration test failures due to Python\botocore dependencies, which will be handled on a separate PR (see reported CI issue).

[patchback]

Backport to stable-3: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 39530ae on top of patchback/backports/stable-3/39530aecf29a4f69da8c07bbd09639652de5b83e/pr-186

Backporting merged PR #186 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/redhat-cop/cloud.aws_ops.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-3/39530aecf29a4f69da8c07bbd09639652de5b83e/pr-186 upstream/stable-3

4. Now, cherry-pick PR [ACA-5022] Configure SonarCloud phase2 #186 contents into that branch:

   $ git cherry-pick -x 39530aecf29a4f69da8c07bbd09639652de5b83e

   If it'll yell at you with something like fatal: Commit 39530aecf29a4f69da8c07bbd09639652de5b83e is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 39530aecf29a4f69da8c07bbd09639652de5b83e

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR [ACA-5022] Configure SonarCloud phase2 #186 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-3/39530aecf29a4f69da8c07bbd09639652de5b83e/pr-186

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-4: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 39530ae on top of patchback/backports/stable-4/39530aecf29a4f69da8c07bbd09639652de5b83e/pr-186

Backporting merged PR #186 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/redhat-cop/cloud.aws_ops.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-4/39530aecf29a4f69da8c07bbd09639652de5b83e/pr-186 upstream/stable-4

4. Now, cherry-pick PR [ACA-5022] Configure SonarCloud phase2 #186 contents into that branch:

   $ git cherry-pick -x 39530aecf29a4f69da8c07bbd09639652de5b83e

   If it'll yell at you with something like fatal: Commit 39530aecf29a4f69da8c07bbd09639652de5b83e is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 39530aecf29a4f69da8c07bbd09639652de5b83e

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR [ACA-5022] Configure SonarCloud phase2 #186 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-4/39530aecf29a4f69da8c07bbd09639652de5b83e/pr-186

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud