feat: Trilogy attribute semantic convention stability

[hannahramadan]

This PR is intended to assist in the transition from the old to new database semantic convention attribute names. Per the database semantic convention stability migration spec, users should be able to set the environment variable OTEL_SEMCONV_STABILITY_OPT_IN to:

• database to emit stable conventions only
• database/dup to emit both old and the stable conventions
• a blank env var will emit old conventions only

The agent is required to maintain this bridge for 6 months and may drop the environment variable in the next major version and emit only the stable database and networking conventions.

This approach was approved for HTTP migration in #1547

Changes (Old -> Stable):

• db.system → db.system.name
• net.peer.name → server.address
• db.name → db.namespace
• db.statement → db.query.text

Removed in stable:

• db.user
• db.instance.id
• peer.service

Added in stable:

• server.port
• error.type
• db.response.status_code

[hannahramadan]

This is a copy of the repo-level .simplecov, minus a guard:

digest.update(ENV.fetch('BUNDLE_GEMFILE', 'gemfile')) if ENV['APPRAISAL_INITIALIZED']

Usually appraisals are testing the same test file with different versions. They are overwriting each other's test coverage but it doesn't matter because it still looks like one file is well tested.

But now different appraisals are testing different source files and still overwriting each other's name, so it looks like code is missing tests.

The fix gives each run a unique name so all 6 results are saved and combined. When we are done with all these duplicate files, we can simply delete this file

[hannahramadan]

I'm just seeing #2272. If that is merged, i'll revert this change, merge that change in, and see if that fixes things