chore: align renovate config with spglib conventions

[lan496]

Summary

• Add separateMultipleMajor: true so a dependency several majors behind gets one PR per major step instead of a single jump.
• Automerge all patch updates, not just github-actions and pre-commit ones.
• Brings .github/renovate.json5 in line with the setup already used in spglib/spgrep and spglib/moyo.

Net diff is .github/renovate.json5 only. The middle two commits add and then revert a [tool.uv] table in pyproject.toml; see "Discarded change" below.

Renovate has never run on this repository. The app is installed on the spglib organization but scoped to selected repositories, and spinforge is not among them; adding it there is a separate step.

Verification

Ran Renovate 44.65.5 against this branch (--dry-run=full, useBaseBranchConfig: merge, schedule forced off) and read the resolved branch configs:

Branch	Update types	automerge
renovate/ci-and-devdependencies	digest, patch, minor	true
renovate/major-7/8/9/10-ci-and-devdependencies	major	false
renovate/lock-file-maintenance-python	lockFileMaintenance	true

separateMultipleMajor is confirmed working: the major updates split into four branches rather than one.

Two caveats on the new patch rule:

• Renovate automerges a group only if every upgrade in it qualifies, so a week where a patch shares the ci-and-devdependencies group with a major will not automerge.
• The dry-run found 26 available updates, all github-actions and pre-commit, and zero pep621. Runtime dependencies are declared with >= ranges, which config:recommended leaves alone, so the general patch rule has little practical effect beyond what the CI/pre-commit rule already covered.

Discarded change

An earlier commit here added an empty [tool.uv] table to pyproject.toml, on the theory that Renovate was not maintaining uv.lock. That was wrong, and it has been reverted.

The evidence came from a local npx renovate that silently resolved to version 37.440.7, which predates uv support entirely (its pep621 manager ships only hatch and pdm processors). On Renovate 44, both this branch and main resolve lockFiles: ["uv.lock"] and updatedArtifacts: ["uv.lock"] with no [tool.uv] table present. The No pdm.lock found line in the logs is the pdm processor declining the project, not a failure.

Test plan

• renovate-config-validator .github/renovate.json5 passes
• After the app is added to this repository, confirm the Dependency Dashboard issue appears and the first patch-level PR is labelled renovate and set to auto-merge

[Claude Code] Generated with Claude Code