opentelemetry-instrumentation-pyramid: avoid duplicate traversal subscribers

[popsiclelmlm]

Description

Fixes #4663.

Summary

Prevent opentelemetry-instrumentation-pyramid from registering duplicate BeforeTraversal subscribers when Pyramid configuration includes run after config.commit().

Reproduction

A Pyramid include can call config.commit(), which resets Pyramid action state. A later config.include(...) creates another configurator and can run the OpenTelemetry callbacks include again. The new regression test simulates that flow and counts _before_traversal subscriber registrations.

Root cause

The instrumentation relied on Pyramid include de-duplication to avoid re-running callbacks.includeme. After config.commit() resets action state, that de-duplication can no longer prevent the callbacks include from registering _before_traversal again for the same registry.

Changes

• Add a registry settings sentinel so callbacks.includeme only registers the BeforeTraversal subscriber once.
• Keep SETTING_TRACE_ENABLED and tween insertion behavior on each include path.
• Add a regression test for an include that calls config.commit() before a later include.
• Add a changelog fragment.

Tests

• /Users/liumin/Documents/OpenSourceContributions/opentelemetry-python-contrib-pika-consumer-wrap/.venv-tox/bin/tox -e py314-test-instrumentation-pyramid
• /Users/liumin/Documents/OpenSourceContributions/opentelemetry-python-contrib-pika-consumer-wrap/.venv-tox/bin/tox -e lint-instrumentation-pyramid
• .tox/lint-instrumentation-pyramid/bin/ruff check instrumentation/opentelemetry-instrumentation-pyramid/src/opentelemetry/instrumentation/pyramid/callbacks.py instrumentation/opentelemetry-instrumentation-pyramid/tests/test_automatic.py
• .tox/lint-instrumentation-pyramid/bin/ruff format --check instrumentation/opentelemetry-instrumentation-pyramid/src/opentelemetry/instrumentation/pyramid/callbacks.py instrumentation/opentelemetry-instrumentation-pyramid/tests/test_automatic.py
• git diff --check

Screenshots/Logs

N/A. This is a unit-level instrumentation fix.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Does This PR Require a Core Repo Change?

• No.

Checklist:

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated