Migrate dev dependencies to new poetry group

[JosephMarinier]

Description:

Migrate dev dependencies from [tool.poetry.dev-dependencies] to new [tool.poetry.group.dev.dependencies] introduced in Poetry 1.2.0.

Checklist:

You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

• ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
• PRE-COMMIT. You ran pre-commit on all commits, or else, you
  ran pre-commit run --all-files at the end.
• USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
  our users.
• DEV CHANGES.
  • Update the documentation if this PR changes how to develop/launch on the app.
  • Update the README files and our wiki for any big design decisions, if relevant.
  • Add unit tests, docstrings, typing and comments for complex sections.

[gabegma]

I get Warning: poetry.lock is not consistent with pyproject.toml. You may be getting improper dependencies. Run poetry lock [--no-update] to fix it. Not you? I don't think that it is linked to your change, but could you update it regardless? Otherwise I can do it.

[JosephMarinier]

Oh right! The poetry.lock is missing some stuff on main. I'll include it in this PR. Thanks!
Then, my change was affecting the content-hash.
Here is the diff: https://github.com/ServiceNow/azimuth/compare/2359f1c14194440d833db15f9f0c08d0885386a8..374076fa4ad469f641983078f736b2147fe40386

[gabegma]

I updated the lock in #463. Thanks!