Issue number: closes #8315

Summary

Changes

CircuitBreakerDynamoDBPersistence lets you rename attributes but assumes a partition-key-only table. Against a single-table design that uses a composite (partition + sort) key, DynamoDB requires the sort key on every call, so the layer can't operate: it fails open on every invocation (logged at WARNING) and the breaker never trips.

This adds optional sort_key_attr and static_pk_value parameters, matching the composite-key support the Idempotency utility already offers, so there's nothing new to learn for anyone using both. Set sort_key_attr and the circuit name is written to the sort key, with static_pk_value in the partition key (default circuit_breaker#{LAMBDA_FUNCTION_NAME}, which namespaces circuits per function; set it to a fixed value to share one circuit across functions). Omit sort_key_attr and behavior is unchanged — the circuit name stays the partition key, exactly as today.

The composite key is threaded through every DynamoDB path the utility uses, not just the read: the get_item read, the conditional put_item that elects the single half-open probe, and the update_item on state transitions. So the breaker works end to end on a composite table.

Also included: docs (docs/utilities/circuit_breaker.md) with a "Using a composite primary key" section, a sample-item table, and share-vs-namespace guidance; and a new example, examples/circuit_breaker_alpha/src/working_with_composite_key.py.

User experience

Before, a composite-key table couldn't be reused — every call failed and the circuit never tripped:

# Fails open on every invocation against a PK + SK table
persistence = CircuitBreakerDynamoDBPersistence(table_name="my-single-table")

Now you opt into the existing single-table layout:

persistence = CircuitBreakerDynamoDBPersistence(
    table_name="my-single-table",
    key_attr="PK",
    sort_key_attr="SK",
    static_pk_value="CIRCUIT_BREAKER",
)

Omitting sort_key_attr keeps today's partition-key-only behavior, so this is fully backward compatible.

Validation

New Stubber-based functional tests cover get_item / put_item / conditional put_item / update_item in both single-key and composite modes, and assert the read-back name comes from the sort key in composite mode. They also cover the sort_key_attr == key_attr guard and the namespaced default value.

poetry run pytest tests/functional/circuit_breaker_alpha tests/unit/circuit_breaker_alpha

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

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.