database instrumentation supports semconv 1.30.

[minimAluminiumalism]

Since currently we still use semconv v1.26.0 which does not include db.collection.name, I defined it as a constant.

NOTICE:
This feature only supports SQL statements that can be parsed by SQL parser packages. If non-standard SQL is used, the span name will fall back to the previous one. For more information, refer here.

Ref: #364

before:

after:

[minimAluminiumalism]

Update to semconv v1.30.

[CLAassistant]

All committers have signed the CLA.

[minimAluminiumalism]

CC @123liuziming

• Defined a new struct SQLMeta, containing the aforementioned properties.
• The LRU algo for sql metadata cache has been added.

Seems that the failed TestLatestDepth cases is unrelated to the PR itself.
A newer version of fasthttp is already released, but the cause of the fiberv2 failure needs to be investigated.

[123liuziming]

CC @123liuziming

• Defined a new struct SQLMeta, containing the aforementioned properties.
• The LRU algo for sql metadata cache has been added.

Seems that the failed TestLatestDepth cases is unrelated to the PR itself. A newer version of fasthttp is already released, but the cause of the fiberv2 failure needs to be investigated.

The underlying fiber uses the fasthttp, I will fix that

[minimAluminiumalism]

@123liuziming

1. Added tests for db collection and db params, related to test/verifier/verifier.go & VerifyDbAttributes().
2. Extracting SQL params on demand through a new env variable OTEL_INSTRUMENTATION_DB_EXPERIMENTAL_ENABLE.
3. Change experimentalAttributesEnabler from instrumenter.NewDefaultInstrumentEnabler() to defaultDbExperimentalAttributesEnabler.

[123liuziming]

LGTM, @NameHaibinZhang feel free to review it

[minimAluminiumalism]

@123liuziming
Could we increase the timeout for running TestPlugins? I've hit the 50-minute limit a few times now.

[123liuziming]

@123liuziming Could we increase the timeout for running TestPlugins? I've hit the 50-minute limit a few times now.

Yes, I will split all the tests into different pipelines later. For now, just increase the timeout for running TestPlugins

[minimAluminiumalism]

@123liuziming Could we increase the timeout for running TestPlugins? I've hit the 50-minute limit a few times now.

Yes, I will split all the tests into different pipelines later. For now, just increase the timeout for running TestPlugins

OK, I'll also temporarily set the timeout to 90 minutes as part of this PR.