chore: Configure Renovate

[Open-Source-Bot]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• .github/actions/setup-test/action.yml (github-actions)
• .github/workflows/build.yml (github-actions)
• .github/workflows/code-check-identified.yml (github-actions)
• .github/workflows/code-check.yml (github-actions)
• .github/workflows/codeql.yml (github-actions)
• .github/workflows/cred-scan.yml (github-actions)
• .github/workflows/github-sanity-scan.yml (github-actions)
• .github/workflows/publish.yml (github-actions)
• pyproject.toml (pep621)
• .github/renovate.json5 (renovate-config-presets)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Ensure that every dependency pinned by digest and sourced from GitHub.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Pin Docker digests.
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
• Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to .github/renovate.json5 in this branch. Renovate will update the Pull Request description the next time it runs.

---

What to Expect

With your current configuration, Renovate will create 2 Pull Requests:

⬆️ deps(github-actions): pin dependencies

• Schedule: ["at any time"]
• Branch name: renovate/pin-dependencies
• Merge into: main
• Upgrade actions/checkout to 8e8c483db84b4bee98b60c0593521ed34d9990e8
• Upgrade astral-sh/setup-uv to 61cb8a9741eeb8a550a1b8544337180c0fc8476b
• Upgrade astral-sh/setup-uv to d0cc045d04ccac9d8b7881df0226f9e82c39688e
• Upgrade github/codeql-action to 5d4e8d1aca955e8d8589aabd499c5cae939e33c7

⬆️ deps(github-actions): update astral-sh/setup-uv action to v7

• Schedule: ["at any time"]
• Branch name: renovate/astral-sh-setup-uv-7.x
• Merge into: main
• Upgrade astral-sh/setup-uv to 61cb8a9741eeb8a550a1b8544337180c0fc8476b

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR has been generated by Renovate Bot.