Stop using 'SonarCloud GH app' integration in favour of GH Actions

[peter-rr]

Why do we need this improvement?

We may need to stop using 'SonarCloud GH app' integration and better start using GH Actions for that purpose.

How will this change help?

This change will avoid having issues when the SonarCloud Code Analysis workflow is not triggered, which prevents the PR's affected from being merged.

See asyncapi/cli#1470

Screenshots

No response

How could it be implemented/designed?

By having a GH workflow that does the same SonarCloud quality checks, with additional workflow_dispatch event support for manual trigger for any repo maintainer.

🚧 Breaking changes

No

👀 Have you checked for similar open issues?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue?

No, someone else can work on it.

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[smoya]

I found a workaround that maybe helps you fix the issue. See asyncapi/parser-js#1033 (comment)

[derberg]

@smoya this workaround did not work in other repos - so I don't think it is the reason