Add mage notice target

[aleksmaus]

What does this PR do?

Adds mage notice target

Why is it important?

Convenient for magicians

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Screenshots

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-11-15T18:14:52.770+0000

• Duration: 53 min 58 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[aleksmaus]

buildkite test this

[aleksmaus]

the integrations tests failure is unrelated to this change, can be merged any time

[pchila]

buildkite test this

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[aleksmaus]

@AndersonQ if you have force merge permissions feels free to merge this PR. CI keeps failing on unrelated to this PR issue.

[AndersonQ]

@aleksmaus I do not have. You can try updating it with main or asking @cmacknz to force merge it

[elastic-sonarqube]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information