Hardcode instrumentation name

[xrmx]

Instead of relying on __name__ when we get tracers / meters / loggers we should hardcode the instrumentation names so that it's not dependent on the file the code is. A good candidate where to add a variable containing that may be the package.py file. We should also add tests to avoid changing that by mistake.

[42Questions]

@xrmx
Agree that __name__ is problematic, and standardising the approach/adding tests.
I've found two instrumentations that resolve incorrectly:

pyramid/callbacks.py

pika/pika_instrumentor.py

Spot checking the other instrumentations most use __name__ only in __init__.py where it happens to resolve correctly.

aio-pika already follows the proposed pattern with a module-level _INSTRUMENTATION_MODULE_NAME constant.

Should botocore's per-service naming (e.g. opentelemetry.instrumentation.botocore.dynamodb) be considered an acceptable variant, or should that also consolidate?