instrumentation wrapping should be idempotent

[realark]

Currently, many of our instrumentation libraries will apply wrapping multiple times if invoked repeatedly. This can lead to duplicated behavior and unintended side effects. Instrumentation should be idempotent—wrapping should only be applied once, regardless of how many times wrap is called.

Tasks:

• Audit existing manual instrumentation to identify where multiple wrapping can occur
• Add safeguards to ensure instrumentation bails out if it has already been applied
• Add unit tests for each wrapper to verify that instrumentation is only applied once

[AbhiPrasad]

Proposal: use a integration / patcher interface inspired from David' work on the Ruby SDK that handles keeping everything idempotent. See https://github.com/braintrustdata/braintrust-sdk-ruby/blob/main/lib/braintrust/contrib/patcher.rb.

Implemented in python way more messily (because the language is less nice) with https://github.com/braintrustdata/braintrust-sdk-python/blob/main/py/src/braintrust/integrations/base.py