feat: split dependency-groups in sections

[laenan8466]

Change

This implements development-dependencies as groups, to enable using only part of the dependencies, e.g. for deploy or ci.

For this we add the groups maintain, ci and docs are added. Documentation is adapted as needed.

Reference - Question #58

Open Question

Group names

Think if you want to keep these names. For uv the default name is dev and there is a flag for this name.

Options:

• One could rename the maintain or ci group to dev.
• Maybe it is an option to combine ci and maintain to dev.

Things to consider:

• What usecases are there, where only part of the dependencies are needed? I can think of: docs deployment, running ci-tests, release-pipeline, ...

Add --all-groups

Should the different uv sync calls have the --all-groups flag? Normally this should be covered by the default-groups, but if users add more groups, these will not be default, e.g. for setup. That can be good and bad.

[pawamoy]

Awesome, just an unimportant style suggestion 🙂

[pawamoy]

I don't expect to use uv flags to select/unselect specific groups locally. In CI we could definitely unselect groups to install only what's necessary depending on the job. We can do that in another PR 🙂 Also yeah we could probably rename maintain to dev, though that's not super important.