AWS bedrock-runtime instumentation for botocore

[xrmx]

trafficstars

This is a tracking issue for the implementation of tracing for Converse and InvokeModel APIs and their respective streaming version. Big difference between the two APIs is that converse is the same for every model while InvokeModel requests and response are different for each model.

• [x] converse #3161
• [x] invokeModel #3200
• [x] converseStream #3204
• [x] InvokeModelWithStreamResponse #3206
• [x] error handling for streaming https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3211
• [ ] close span also when closing stream by calling __wrapped__.close()
• [ ] server attributes (generic for botocore?), also in metrics
• [x] user events https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3258
• [x] system events https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3266
• [x] choice events https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3275
• [x] tool calls https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3302
• [ ] investigate amazon.nova not using tool calls with invokeModel
• [x] metrics https://github.com/open-telemetry/opentelemetry-python-contrib/pull/3326
• [ ] proper semconv attribute for cloud region
• [ ] http stable semconv opt-in support
• [ ] more models for InvokeModel* ?
• [ ] other bedrock runtime apis?