Fix setuptools-scm version resolution in CI workflows

[Copilot]

setuptools-scm derives the package version from git tags, but actions/checkout defaults to depth=1 which strips tags. This caused the publish workflow to build with a stale version (0.9.2 instead of 0.10.0).

• Add fetch-depth: 0 to checkout in python-publish.yml and python-package.yml so the full tag history is available to setuptools-scm

After merge, re-create the GitHub Release from the v0.10.0 tag to trigger a correct publish.

[Copilot]

Pull request overview

This PR updates the GitHub Actions CI workflows to ensure setuptools-scm can correctly derive the project version from git tags by making actions/checkout fetch the full repository history (including tags). This addresses incorrect/stale versioning during builds/publishing when the default shallow checkout (depth=1) omits tag history.

Changes:

• Configure actions/checkout with fetch-depth: 0 in the publish workflow so release builds have full tag history available.
• Configure actions/checkout with fetch-depth: 0 in the package/test workflow to keep version resolution consistent during CI installs/build steps.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.github/workflows/python-publish.yml	Fetch full git history/tags during release publish to allow setuptools-scm to resolve the correct version.
.github/workflows/python-package.yml	Fetch full git history/tags in CI runs to avoid shallow-clone version resolution issues.