Client dynamodb/test changes

[lucianlature-endava]

Issue

#7845

Description

This change brings the local e2e dependency on DynamoDB Local.
Added scripts/dynamodb-local/docker-compose.yml using amazon/dynamodb-local:latest.
Added scripts/dynamodb-local/dynamodb.sh to start DynamoDB Local and wait for readiness.
Added scripts/dynamodb-local/down.sh to stop the stack.
Added scripts/dynamodb-local/README.md with start/stop usage.
Updated clients/client-dynamodb/package.jsonsotest:e2e:local` uses the new DynamoDB Local flow and exports endpoint/credential env vars.

Testing

Tested with:

• docker compose -f scripts/dynamodb-local/docker-compose.yml config
  Result: compose file valid.
• bash scripts/dynamodb-local/dynamodb.sh
  Result: container starts and readiness check succeeds on http://localhost:8000.
• bash scripts/dynamodb-local/down.sh
  Result: stack stops cleanly.
• yarn test:e2e:local (from clients/client-dynamodb)
  Result: infra startup succeeds.

Checklist

• If the PR is a feature, add integration tests (*.integ.spec.ts) or E2E tests.
• It's not a feature.
• My E2E tests are resilient to concurrent i/o.
• I didn't write any E2E tests.
• I added access level annotations e.g. @public, @internal tags and enabled doc generation on the package. Remember that access level annotations go below the description, not above.
• I didn't add any public functions.
• Streams - how do they work?? My WebStream readers/locks are properly lifecycled. Node.js stream backpressure is handled. Error handling.
• No streams here.

---

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