Migrate sphinx documentation system to material for mkdocs

[arandito]

Description

This PR merges the feat/migrate-sphinx-to-mkdocs feature branch into develop, completing the migration from the existing Sphinx documentation system to Material for Mkdocs

Related PRs in feat/migrate-sphinx-to-mkdocs:

• Update clients to support Google-style docstrings. #24
• Generate top-level and individual API reference docs for all SDK clients #36

In addition to the documentation migration, this PR:

• Rebases the feature branch onto the latest develop
• Regenerates all clients using the latest service models and code generator updates from Switch to Google-style docstrings with Markdown and remove Sphinx/RST generation smithy-lang/smithy-python#592
• Fixes minor logging inconsistencies and removes leftover files from rebase

This PR and the related code generator update will be merged simultaneously.

Testing

• Ran integration tests and confirmed they succeed for Transcribe Streaming and Bedrock Runtime.
• Confirmed documentation generates for top-level site and for individual clients.

How to Generate Docs

For top-level client docs, execute these commands in the root level of this repo. For individual client documentation, execute these commands in each client's directory.

# Install docs dependencies
make docs-install

# Build static HTML to site/
make docs

# Serve documentation locally to port 8000
make docs-serve

# Clean up artifacts
make docs-clean

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[jonathan343]

Looks good, just had a couple of comments and suggestions. We should also include related changelog entries to each client so they're included in our next release.

[jonathan343]

Super nit / not blocking:

Suggested change

	margin-top: 0;
	margin-top: 0;

We should indent this for all three clients

[arandito]

Fixed!

[jonathan343]

These packages don't have lock files. We should be using uv pip instead of uv sync. This also prevents us from generating unwanted uv.lock files.

Suggested change

	uv sync --group docs
	uv pip install -e . --group docs

[arandito]

That makes sense. I updates this and added the --no-sync flag to the uv run commands in the individual clients to avoid creating uv.lock files from there as well.

[jonathan343]

Why is this here and not in the nested clients?

[arandito]

This enables content tabs in the "All Available Clients" page for the top-level documentation site. We don't need this plugin in the individual clients since we don't use content tabs anywhere.

With pymdownx.tabbed:

Without: