Additional dlls getting signed in the codesigning (mds) job (for abstractions and logging).

[cheenamalhotra]

I do still see extra dlls getting signed in the mds job (for abstractions and logging). Maybe we can correct that in a follow up PR. All other jobs look good.
https://sqlclientdrivers.visualstudio.com/ADO.Net/_build/results?buildId=142444&view=logs&j=67e5cce3-cf4d-502d-4e4e-0012da109ce2&t=faf3e756-f191-5b4b-8a51-37897c063709

Originally posted by @mdaigle in #3998 (review)

[samsharma2700]

The MDS build job uses an older ESRP signing template (esrp-code-signing-step.yml) that searches from $(REPO_ROOT) with the pattern Microsoft.Data.SqlClient*.dll. Because the search is recursive across the entire repo tree, it picks up not only the intended Microsoft.Data.SqlClient.dll but also Microsoft.Data.SqlClient.Extensions.Logging.dll and Microsoft.Data.SqlClient.Extensions.Abstractions.dll that exist in intermediate build output directories.

The newer csproj-based jobs (Logging, Abstractions, Azure) use a different template (compound-esrp-dll-signing-step.yml) that scopes signing to $(BUILD_OUTPUT)/Package/bin with an exact DLL name, so they don't have this problem.

The fix is to narrow the MDS job's sourceRoot parameter from $(REPO_ROOT) to the MDS-specific build output path, so the wildcard pattern only matches DLLs built by that job.
Will send a PR soon.