chore(acr): add backstage app to workspace

[christoph-jerolimov]

Hey, I just made a Pull Request!

I added a backstage app to the acr/Azure Container Registry workspace to simplify the development process.

The workspace contains a catalog entity with the azure-container-registry/repository-name annotation.

Actually, it still requires an ACR instance and access token.

To solve some compile issues, I followed backstage/backstage#8694 and changed the import of useAsync from react-use.

For that change, I added a changeset.

I will raise other PRs for the planned UI improvements.

✔️ Checklist

• A changeset describing the change and affected packages. (more info)
• Added or updated documentation
• Tests for new functionality and regression tests for bug fixes
• Screenshots attached (for UI changes) => No UI change in this plugin.
• All your commits have a Signed-off-by line in the message. (more info)

[backstage-goalie]

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
app	workspaces/acr/packages/app	none	v0.0.3
backend	workspaces/acr/packages/backend	none	v0.0.0
@backstage-community/plugin-acr	workspaces/acr/plugins/acr	patch	v1.8.7

[ciiay]

Verified the changes are working as expected. Thank you.

/lgtm

[schultzp2020]

@christoph-jerolimov instead of react-use consider using @react-hookz/web instead. RE: backstage/backstage#25650

[christoph-jerolimov]

@christoph-jerolimov instead of react-use consider using @react-hookz/web instead. RE: backstage/backstage#25650

Hey @schultzp2020, thanks, I can take look as a next step for the acr-plugin, but here I like to focus on the workspace. Can you merge that PR?

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!