chore(deps): update dependency nunit3testadapter to 6.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
NUnit3TestAdapter (source)	6.2.0 → 6.3.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "after 9pm every weekday,every weekend,before 7am every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[argus-pr]

✅ Reviewed 652186b — nothing to flag.

🤖 @argus-pr — automated AI assistant; replies may be wrong.

[argus-pr]

@argus-pr review — 652186b · model deepseek-v4-flash-vision-exp

Summary — This pull request bumps the NUnit3TestAdapter package from 6.2.0 to 6.3.0 in the test project. The change is a single-line version update with no other modifications.

Risk surface — facts about this change, not findings. A reviewer should start here:

• Dependency changes: dependency manifest(s) changed — verify added/updated dependencies — src/SqlInliner.Tests/SqlInliner.Tests.csproj.

No issues found at or above the MEDIUM threshold. ✅
That is this review finding nothing on the risk surface above — not a finding that there is nothing there.

Severity	Posted	Suppressed
CRITICAL	0	0
HIGH	0	0
MEDIUM	0	0
LOW	0	0

What this review did — 1 of 1 pass(es) over 1 file(s)

• Passes completed: 1 of 1
• Files reviewed: 1 of 1
• Tool calls made while investigating: 0

What it chose to check — the panel's own reading of what mattered here, planned before it looked. Feedback for a reviewer, not a guarantee that each check was completed:

• Confirm the exact diff in the test project file (version bump 6.2.0 → 6.3.0, no other changes). (via get_pr_diff for src/SqlInliner.Tests/SqlInliner.Tests.csproj)
• Read the full csproj to verify the package reference context, target frameworks, and whether other test packages (NUnit, Microsoft.NET.Test.Sdk) are compatible with the new adapter version. (via read_file src/SqlInliner.Tests/SqlInliner.Tests.csproj)
• Check for central package management or lock files that must be updated in tandem (Directory.Packages.props, packages.lock.json, nuget.config). (via glob for Directory.Packages.props, packages.lock.json, nuget.config; grep for NUnit3TestAdapter)
• Check CI/build configuration for test execution to ensure the adapter version is picked up consistently and no pinned version elsewhere conflicts. (via grep for NUnit3TestAdapter and dotnet test across .github/workflows and repo config files)

---

🤖 Reviewed by @argus-pr (AI, model deepseek-v4-flash-vision-exp) — automated, may be wrong. Reply @argus-pr help for commands.