fix(aws): restore Transcribe STT on transcribe-streaming 0.11

[longcw]

Problem: AWS Transcribe STT cannot start on aws-sdk-transcribe-streaming 0.10.0 or later. 0.10.0 dropped the Config export and 0.11.0 dropped the TranscribeStreamingClient alias, so the module import fails and STT() raises a misleading ImportError: The 'aws_sdk_transcribe_streaming' package is not installed.

Fix: Raise the floor to 0.11.0, import AsyncTranscribeStreamingClient and AsyncTranscribeStreamingConfig directly, and build the config with await Config.resolve(...). 0.11.0 makes AIOHTTPClient the default transport, which cannot carry a bidirectional stream, so StartStreamTranscription now gets the SpeechStream's AWSCRTHTTPClient through transport=, closed once in aclose().

Replaces #7074, whose transport diagnosis this keeps. Close #7072.

Context for reviewing and coding agents

How to see the failure

Install aws-sdk-transcribe-streaming 0.11.0, then run the module. On main all five tests fail, because livekit.plugins.aws.stt sets _AWS_SDK_AVAILABLE = False and every test constructs an STT.

uv run pytest tests/test_plugin_aws_stt.py --unit

The new test asserts the resolved config carries the SpeechStream's own AWSCRTHTTPClient, and that the client is closed exactly once, after aclose(). The close count guards the restart path: AWS ends a stream after 15 seconds of silence and _run loops, so a close inside the loop leaves the next attempt with a dead HTTP client.

What else the lock bump moves

transcribe-streaming 0.11.0 needs smithy-core~=0.8.0, while the locked 0.7.0 needed ~=0.6.0. uv therefore also lifts aws-sdk-bedrock-runtime 0.7.0 to 0.11.0, plus smithy-aws-core, smithy-http, and smithy-json. The only other consumer of bedrock-runtime is livekit-plugins/livekit-plugins-aws/livekit/plugins/aws/experimental/realtime/realtime_model.py, which #7076 already made work on 0.11.

Why the floor moved instead of a version ladder

The client name, the config name, and the config constructor all differ across 0.9.0, 0.10.0, and 0.11.0. A ladder that keeps >=0.2.0 needs nested import fallbacks and a hasattr(Config, "resolve") check at runtime. One floor makes the imports direct and leaves the config path with no branch.

What the raise costs

A Python 3.12+ install that holds transcribe-streaming below 0.11.0 must upgrade. STT is already dead on 0.10.0 and 0.11.0, so only pins at 0.9.0 and earlier lose a working version. The dependency added is smithy-http[awscrt], not awscrt, because 0.11.0 moved the CRT transport behind an extra and smithy-http owns the awscrt~=0.32.0 bound.