[MNT] Prevents assignment on Restricted Labels

[kavya-r30]

Reference Issues/PRs

Contributes #2697

What does this implement/fix? Explain your changes.

Prevents assignment of issues where certain restricted labels are present when calling aeon-actions-bot
restricted_labels = {"meta-issue"}

This solves the first part of the issue #2697

Does your contribution introduce a new dependency? If yes, which one?

Any other comments?

PR checklist

For all contributions

• I've added myself to the list of contributors. Alternatively, you can use the @all-contributors bot to do this for you after the PR has been merged.
• The PR title starts with either [ENH], [MNT], [DOC], [BUG], [REF], [DEP] or [GOV] indicating whether the PR topic is related to enhancement, maintenance, documentation, bugs, refactoring, deprecation or governance.

For new estimators and functions

• I've added the estimator/function to the online API documentation.
• (OPTIONAL) I've added myself as a __maintainer__ at the top of relevant files and want to be contacted regarding its maintenance. Unmaintained files may be removed. This is for the full file, and you should not add yourself if you are just making minor changes or do not want to help maintain its contents.

For developers with write access

• (OPTIONAL) I've updated aeon's CODEOWNERS to receive notifications about future changes to these files.

[aeon-actions-bot]

Thank you for contributing to aeon

I have added the following labels to this PR based on the title: [ $\color{#EC843A}{\textsf{maintenance}}$ ].

The Checks tab will show the status of our automated tests. You can click on individual test runs in the tab or "Details" in the panel below to see more information if there is a failure.

If our pre-commit code quality check fails, any trivial fixes will automatically be pushed to your PR unless it is a draft.

Don't hesitate to ask questions on the aeon Slack channel if you have any.

PR CI actions

These checkboxes will add labels to enable/disable CI functionality for this PR. This may not take effect immediately, and a new commit may be required to run the new configuration.

• Run pre-commit checks for all files
• Run mypy typecheck tests
• Run all pytest tests and configurations
• Run all notebook example tests
• Run numba-disabled codecov tests
• Stop automatic pre-commit fixes (always disabled for drafts)
• Disable numba cache loading
• Push an empty commit to re-run CI checks

[MatthewMiddlehurst]

Please ensure that this works on your fork first.

[MatthewMiddlehurst]

See #2703

[kavya-r30]

@MatthewMiddlehurst
I created a mirror and build the workflow and app to test out the issue_assign actions since it dint let me do on my fork due to github token:

1. Test for meta-issue label: Test for meta-issue label kavya-r30/aeon-test#3
2. Test without meta-issue: Test without meta-issue kavya-r30/aeon-test#4
3. Test for multiple issue: Test for multi kavya-r30/aeon-test#5

[MatthewMiddlehurst]

Please remove the branches or workflow pinging for stale branches https://github.com/kavya-r30/aeon-test/issues