Update acs workspace to commit bad551c for backstage 1.40.2 on branch release-1.8

[github-actions]

Update acs workspace at commit backstage/community-plugins@bad551c for backstage 1.40.2 on branch release-1.8.

This PR was created automatically.

⚠️ Manual re-approval required
An override exists at workspaces/acs/backstage.json. This upgrade is a Best-Effort match.
Since the previous version was manually verified to work against the target Backstage version, please review and test again before merging.
The overridden backstage.json has been removed because it's out-of-sync (1.42.5) with the Backstage version of the new source commit (1.40.2).
A new one should be added after testing the plugins against the target Backstage version.
Don't forget to also update the repo-backstage-version field in source.json accordingly.

Click on the following link to see the source diff it introduces: backstage/community-plugins@d27bb85...bad551c.

Before merging, you need to export the workspace dynamic plugins as OCI images,
and if possible test them inside a RHDH instance.

To do so, you can use the /publish instruction in a PR review comment.
This will start a PR check workflow to:

• export the workspace plugins as dynamic plugins,
• publish them as OCI images
• push the oci-images in the GitHub container registry with a PR-specific tag.

[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

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.