[receiver/sqlserver] x509 negativeserial issue

[sincejune]

Description

SQL Server receiver now requires a positive serial number for X509 certificates due to the Go 1.23 adoption in #38099

Link to tracking issue

n/a

Testing

n/a

Documentation

n/a

[sincejune]

SQL Server docker users may run into an issue that the collector fails to parse certificate from server due to x509: negative serial number. That's because we adopted Go 1.23 starting from contrib v0.121.0:

Before Go 1.23, ParseCertificate accepted certificates with negative serial numbers.
This behavior can be restored by including "x509negativeserial=1" in the GODEBUG environment variable.

references:

1. https://pkg.go.dev/crypto/x509#ParseCertificate
2. Default TLS cert uses negative serial number microsoft/mssql-docker#895

[sincejune]

This change is actually not in the release notes of Go 1.23.
Since the SQL Server receiver uses the underlying scraperhelper dependency (which raises negative serial number issue) in core repo, should we consider adding a note at the project level?

cc @atoulme @bogdandrutu @mx-psi @songy23

[MovieStoreGuy]

This change is actually not in the release notes of Go 1.23. Since the SQL Server receiver uses the underlying scraperhelper dependency (which raises negative serial number issue) in core repo, should we consider adding a note at the project level?

cc @atoulme @bogdandrutu @mx-psi @songy23

So this raises an interesting question, do we raise a breaking change for each component that would be using the impacted package, or raise it a breaking change for the project.

I'll delegate that to @open-telemetry/collector-approvers to see what they say.