Add CI package pipeline for building and publishing NuGet packages

[paulmedynski]

Adds a new top-level pipeline at eng/pipelines/ci/package/sqlclient-package.yml that:

• Runs on pushes to GitHub main and ADO internal/main branches (batched)
• Runs nightly at 00:00 UTC on those same branches
• Cleans the packages/ directory before building
• Uses build.proj Pack target with ReferenceType=Package
• On internal builds, downloads the signing key and strong-name signs assemblies
• Publishes all produced .nupkg/.snupkg files as a pipeline artifact

Tested ADO.Net project runs here:

• Linux: https://dev.azure.com/SqlClientDrivers/ADO.Net/_build/results?buildId=154236&view=results
• Windows: https://dev.azure.com/SqlClientDrivers/ADO.Net/_build/results?buildId=154237&view=results
• All pipeline parameters were tested between these 2 runs.

We can't test Public project runs until this merges, because we can only create new pipelines based on GitHub for YAML files on main.

[Copilot]

Pull request overview

Adds a new CI pipeline that builds and publishes NuGet packages via build.proj in ReferenceType=Package mode, alongside a broader refactor to make package-mode builds self-sustaining: version flow is unified through import-guarded Versions.props files imported early by Directory.Packages.props, all Pack* targets now mirror their output into the local packages/ feed and gain DependsOn chains so dependent packages restore against freshly built nupkgs, and many test/csproj files now switch between ProjectReference and PackageReference for Microsoft.SqlServer.Server based on ReferenceType. A new signed test category gates UDT tests that require a strong-name-signed Microsoft.SqlServer.Server.

Changes:

• New pipeline eng/pipelines/ci/package/sqlclient-package.yml (push to main/internal/main, nightly, optional strong-name signing on internal builds).
• build.proj and Directory.Packages.props overhaul: package-mode DependsOn/Pack mirroring, central SqlServerPackageVersion token wiring, category!=signed filter for unsigned builds.
• Threading of sqlServerArtifactsName/sqlServerPackageVersion through existing CI templates, and reference-mode switching for Microsoft.SqlServer.Server across csprojs (including nuspec token $SqlServerPackageVersion$).

Reviewed changes

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
eng/pipelines/ci/package/sqlclient-package.yml	New CI pipeline that packs all packages and publishes Packages artifact.
build.proj	Adds package-mode DependsOn chains, output mirroring to packages/, category!=signed filter, and PackageVersionSqlServer threading.
Directory.Packages.props	Imports all Versions.props in Package mode to centrally manage sibling package versions.
doc/Directory.Packages.props, doc/samples/Microsoft.Data.SqlClient.Samples.csproj	Pin and reorganize Microsoft.SqlServer.Server package usage.
src/Directory.Build.props	Comment clarifying FileVersionBuildNumber ordering relative to Directory.Packages.props.
src/**/Versions.props (×6)	Add per-product import-guard property to prevent double evaluation.
src/**/*.csproj (Logging, Abstractions, Azure, AKV, SqlServer, SqlClient src/ref/notsupported)	Conditional Versions.props import using the new guard; SqlClient ref/notsupported gain SqlServer reference; nuspec token updated.
src/Microsoft.Data.SqlClient/src/Microsoft.Data.SqlClient.csproj	Adds SqlServer version import, trim, validation error, and nuspec token replacement.
src/Microsoft.Data.SqlClient/src/Microsoft.Data.SqlClient.nuspec	Replaces hard-coded 1.0.0 with $SqlServerPackageVersion$ token.
src/Microsoft.Data.SqlClient/tests/UnitTests/...csproj	Adds ValidateReferenceType target and project reference to Microsoft.SqlServer.Server.
src/Microsoft.Data.SqlClient/tests/ManualTests/...csproj	Reference-mode switching for Microsoft.SqlServer.Server (top-level and UDT projects).
src/Microsoft.Data.SqlClient/tests/Common/Microsoft.Data.SqlClient.TestCommon.csproj	Enables ImplicitUsings.
src/Microsoft.Data.SqlClient/tests/ManualTests/SQL/UdtTest/SqlServerTypesTest.cs, FunctionalTests/SqlDataRecordTest.cs	Adds [Trait("Category", "signed")] on NETFRAMEWORK for UDT tests requiring signed SqlServer assembly.
eng/pipelines/**/*.yml (ci-core, build-sqlclient/azure stages, ci-run-tests stage/job, ci-build-nugets, ci-project-build, run-all-tests, test-azure-package job)	Thread new sqlServerArtifactsName/sqlServerPackageVersion parameter and download the SqlServer artifact for package-mode test/build flows.

[Copilot]

Pull request overview

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.68%. Comparing base (520b40b) to head (5815f60).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4292      +/-   ##
==========================================
- Coverage   66.50%   64.68%   -1.83%     
==========================================
  Files         284      279       -5     
  Lines       43301    66219   +22918     
==========================================
+ Hits        28796    42831   +14035     
- Misses      14505    23388    +8883     

Flag	Coverage Δ
CI-SqlClient	?
PR-SqlClient-Project	64.68% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

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

[cheenamalhotra]

This reminds me we should be building for a forward release, i.e. published packages should be named as '7.1.0-preview2.xxxxxx' instead of '7.1.0-preview1.xxxxxx'.

Once we have bumped up the versioning, we should also start publishing Nightly built packages to an ADO Artifact feed that's available to public as well - in public project. I don't know if running this pipeline in CI would be any help in long term, as Nightly build and publishing will serve its purpose.

Overall this pipeline is doing its job well, we just need to come on agreement with versioning bump to happen right after we release something (or with release notes), before the first 'vNext' nightly build is published.

[cheenamalhotra]

A few minor changes I would suggest maybe now or future.

[cheenamalhotra]

This should not build in debug mode I think.

[cheenamalhotra]

Can we omit running this if there were no changes merged in last 24 hours?