Rm repeated link defs

Author: tammy-baylis-swi

instrumentation/opentelemetry-instrumentation-dbapi/src/opentelemetry/instrumentation/dbapi/__init__.py

@@ -62,8 +62,6 @@
 `instrumentation`_. There is no need to opt in at the DB-API level unless setting up
 its integration directly.
 
-.. _instrumentation: https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation
-
 If using DB-API instrumentation directly, you can optionally enable sqlcommenter which
 enriches the query with contextual information. Queries made after setting up
 trace integration with sqlcommenter enabled will have configurable key-value pairs
@@ -98,8 +96,6 @@
 `instrumentation`_. There is no need to configure at the DB-API level unless setting up
 its integration directly.
 
-.. _instrumentation: https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation
-
 If using DB-API instrumentation directly, the key-value pairs appended to the query
 can be configured using ``commenter_options``. When sqlcommenter is enabled, all
 available KVs/tags are calculated by default. ``commenter_options`` supports *opting out*
@@ -156,8 +152,6 @@
 `instrumentation`_. There is no need to opt in at the DB-API level unless setting up
 its integration directly.
 
-.. _instrumentation: https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation
-
 If using DB-API instrumentation directly and sqlcommenter is enabled, you can opt into
 the inclusion of sqlcomment in the query span ``db.statement`` attribute for your needs.
 If ``commenter_options`` have been set, the span attribute comment will also be configured