Use new OpenTelemetry semantic conventions for database spans

[bgrainger]

https://opentelemetry.io/docs/specs/semconv/database/database-spans/

Changes appear to be:

Removed	Added	Notes
n/a	db.instance.id	The actual DB instance, e.g., if individual nodes in a cluster can be distinguished
net.sock.peer.addr	network.peer.address
net.sock.peer.port	network.peer.port
net.transport	network.transport	Values have changed, e.g., tcp instead of ip_tcp
net.sock.family	network.type	Values have changed, e.g., ipv4 or ipv6 instead of inet or inet6
net.peer.name	server.address	Appears to have some overlap with network.peer.address
net.peer.port	server.port	Some overlap with network.peer.port

An environment variable, OTEL_SEMCONV_STABILITY_OPT_IN "SHOULD" be used to control whether old, new, or both attributes should be emitted.