chore: pin packages at major-minor versions

Explanation of changes

Pinning some dev dependencies:

[project.optional-dependencies]
test = [
    "pytest~=8.3",
    "pytest-mock~=3.14",
    "diff-cover~=5.0",
    "pytest-mpl~=1.1",
    "pytest-cov~=6.0",
    "pytest-xdist~=3.6",
]

docs = [
 "jupyter_sphinx>=0.4.0",
 "jupytext~=1.14",
 "pydata-sphinx-theme~=0.13",
 "myst-nb~=0.17",
 "hvplot~=0.8",
 "rich[jupyter]~=13.4",
 "scanpydoc>0.12.1",                # 0.12.0 and 0.12.1 parse return type in docstrings incorrectly. see also https://github.com/theislab/scanpydoc/issues/120.
 "sphinx~=6.2",
 "sphinx-autoapi~=3.2",
 "sphinx-autobuild~=2024.10",
 "sphinx-autodoc-typehints~=2.2",   # required by either sphinx.ext.autodoc or sphinx.ext.napoleon
 "sphinx-copybutton~=0.5",
 "sphinx-design~=0.6",
 "sphinx-jsonschema~=1.19",
 "sphinx-togglebutton~=0.3",
 "sphinxcontrib-bibtex~=2.6",
 "sphinxcontrib-mermaid~=0.9",
 "quantify_scheduler[zhinst]",

]

dev = [
    "pre-commit~=4.1",
    "pre-commit-hooks~=5.0",
    "pyright!=1.1.396",
    "ruff~=0.10",
    "quantify-scheduler[docs,test]",
    "quantify_scheduler[zhinst]",
]

zhinst = [
 "zhinst==21.8.20515; python_version<'3.10'",
 "zhinst-qcodes==0.1.4; python_version<'3.10'",
 "zhinst-toolkit==0.1.5; python_version<'3.10'",
]

and removed the following dependencies:

coverage
pylint
astroid

Also moved some dependencies from dev into either test, or docs if it made sense to me.

Related links and Jira ticket

https://qblox.atlassian.net/browse/QTFY-228

---

Merge checklist

See also merge request guidelines

• Merge request has been reviewed (in-depth by a knowledgeable contributor), and is approved by a project maintainer.
• New code is covered by unit tests (or N/A).
• New code is documented and docstrings use numpydoc format (or N/A).
• New functionality: considered making private instead of extending public API (or N/A).
• Public API changed: added @deprecated and entry in deprecated code suggestions (or N/A).
• Newly added/adjusted documentation and docstrings render properly (or N/A).
• Pipeline fix or dependency update: post in #software-for-developers channel to merge main back in or update local packages (or N/A).
• Tested on hardware (or N/A).
• CHANGELOG.md for breaking changes and AUTHORS.md have been updated (or N/A).
• Update Hardware backends documentation if backend interface change or N/A
• Check whether performance is significantly affected by looking at the Performance metrics results.
• Windows tests in CI pipeline pass (manually triggered by maintainers before merging).
  • Maintainers do not hit Auto-merge, we need to actively check as manual tests do not block pipeline

---

For reference, the issues workflow is described in the contribution guidelines.