DynamoDB and celld providers on Axum meet the record contract #473

Summary

DynamoDB and celld providers on Axum meet the record contract, each key's partition being its DynamoDB partition key.

Behavior

Both meet the EZI-2a contract on Axum. DynamoDB uses each key's partition as its partition key, so writes spread across partitions and no item is updated by every insert (AX-4).

Acceptance criteria

• The contract suite passes against both on Axum, listing within a partition is strong, and keys in different partitions land in different DynamoDB partitions

Dependencies

Blocked by:

• KvStore record contract with listing strong within a partition #472 KvStore record contract with listing strong within a partition (new in this plan)
• Add native AWS configuration, secret, and ordinary KV store providers #410 Add native AWS configuration, secret, and ordinary KV store providers
• Add native celld configuration and KV store providers #437 Add native celld configuration and KV store providers
• PR Add native celld config, KV and conditional record providers #422 Add native celld config, KV and conditional record providers, which carries the celld record operations of closed Extract conditional celld record operations from demo RC #463

Blocks:

• Integration-branch revision with the record contract: EZI-2a and EZI-2b #489 Integration-branch revision with the record contract: EZI-2a and EZI-2b (new in this plan)
• Portable DynamoDB and celld providers over EdgeZero's outbound HTTP, verified on Fastly #474 Portable DynamoDB and celld providers over EdgeZero's outbound HTTP, verified on Fastly (new in this plan)

Related

• Needed by Server-side identity on every adapter trusted-server#1558, server-side identity on every adapter. Planned in wave 4 (MVP: Fastly and Axum); priority P1, size L.
• Work in progress: Add native celld config, KV and conditional record providers #422 Add native celld config, KV and conditional record providers
• Requirement EZI-2b in the design.