v2.1.0-alpha.9

GSI support

v2.1.0-alpha.6

Add ScanIndexForward support to FakeDynamoDBInterface

Implement the ScanIndexForward parameter for query operations in
FakeDynamoDBInterface to match DynamoDB behavior:

- Add 'ScanIndexForward' to supported parameters for queryOnePage and
  queryAllPages
- Implement sorting logic in executeQuery based on the ScanIndexForward
  parameter
- Query results are now sorted by sort key (if table has one)
- ScanIndexForward defaults to true (ascending order)
- When false, results are returned in descending order
- Add compareValues method to support sorting of strings and numbers
- Add getSkName method to FakeTable to expose sort key name

Added comprehensive tests:
- Test ascending order with ScanIndexForward=true
- Test descending order with ScanIndexForward=false
- Test default behavior (ascending when not specified)
- Test with numeric sort keys
- Test with sort key conditions
- Test queryAllPages with ScanIndexForward

All tests pass (132 tests total, including 6 new ScanIndexForward tests)

v2.1.0-alpha.5

Add support for ignored performance/metrics parameters

Updated FakeDynamoDBInterface to accept (but ignore) the following
parameters that are purely informational or related to AWS optimization:

- ReturnConsumedCapacity: Added to get, put, delete, batchWrite,
  transactionWrite, queryOnePage, queryAllPages, scanOnePage, scanAllPages
  - Returns information about consumed capacity units
  - No meaning in an in-memory implementation

- ReturnItemCollectionMetrics: Added to put, delete, batchWrite,
  transactionWrite
  - Returns statistics about item collection sizes
  - No meaning in an in-memory implementation

- ClientRequestToken: Added to transactionWrite
  - Used for making operations idempotent
  - In-memory operations are already atomic/instant

These parameters are now accepted to maintain compatibility with real
DynamoDB operations but are not processed as they have no meaning in
a fake in-memory implementation.

Updated unit tests to verify that these parameters are accepted for all
applicable operations instead of throwing errors.

v2.1.0-alpha.4

Add ConsistentRead parameter support to FakeDynamoDBInterface

Updated FakeDynamoDBInterface to accept (but ignore) the ConsistentRead
parameter for operations that support it in DynamoDB:
- get
- queryOnePage
- queryAllPages
- scanOnePage
- scanAllPages

The parameter is now accepted to maintain compatibility with real DynamoDB
operations, but it is not processed as the fake implementation does not
distinguish between strongly consistent and eventually consistent reads.

Updated unit tests to verify that ConsistentRead is accepted for all
applicable operations instead of throwing an error.

v2.1.0-alpha.3

Start query implementation

v2.1.0-alpha.2

Consolidate fake db interface and table

Also more tests

v2.1.0-alpha.1

Consolidate fake db interface and table

Also more tests

v2.1.0-alpha.8

Fix GitHub Pages artifact upload path

The generate-docs script runs in the workspace context, which creates
the docs at packages/dynamodb-entity-store/docs/, not at the root level.
Updated the upload-pages-artifact path to reference the correct location.

Fixes: tar: docs/: Cannot open: No such file or directory