[GOV] Supporting Developer role

[MatthewMiddlehurst]

Adds a new role which is essentially just giving a person write access. Difference from core devs:

• No access to the core developer or voting Slack channels
• Any core dev can nominate someone for the role, just have to notify other developers in Slack and make a PR
• No vote as long as there is no veto by any core developer. That veto right remains for the duration and can be invoked if anyone thinks they are a detriment (i.e. acting like an ass or abusing review powers)
• Removed with inactivity

Essentially a stepping stone between regular contributor and core dev. Main target would be stuff like PhD students, interns or just people we want to get a bit more involved in the project without going through the whole process. Of course if people want to become core devs the same process still exists.

[aeon-actions-bot]

Thank you for contributing to aeon

I did not find any labels to add that did not already exist. If the content of your PR changes, make sure to update the labels accordingly.

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