Feat backport monorepo annotations into acr

[dudinea]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.
• Optional. My organization is added to USERS.md.
• Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

[codecov]

Codecov Report

❌ Patch coverage is 25.31646% with 59 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
acr_controller/service/acr_service.go	27.77%	48 Missing and 4 partials ⚠️
acr_controller/controller/controller.go	0.00%	3 Missing ⚠️
...commands/application_change_revision_controller.go	0.00%	3 Missing ⚠️
acr_controller/server.go	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!