Newer SemConv releases changed attribute names for DB as part of the stabilization. Example: https://github.com/open-telemetry/semantic-conventions/releases/tag/v1.30.0
With that, our logic does not derive span.type and subtype correctly with the newer SemConv version.
In the intake weekly we also agreed to follow the way to handle multiple versions the same way in the enrichment as done in elastic/apm-data#440.
TODO: Add logic to handle the new field names as well.