Add ConsistentRead support for GetItem, Query, and BatchGetItems operations

[Copilot]

Description

Adds support for DynamoDB strongly consistent reads in getItem, query, queryWithCursor, and batchGetItems operations per AWS SDK specification.

Implementation:

• All read operations accept consistentRead as a separate optional parameter (not part of Filter object)
• getItem() accepts optional consistentRead parameter (3rd argument)
• batchGetItems() accepts optional consistentRead parameter (3rd argument)
• query() accepts optional consistentRead parameter (3rd argument, after indexName)
• queryWithCursor() accepts optional consistentRead parameter (3rd argument, after indexName)

Usage:

// Query with consistent read
await dynamoHelper.query(
  { where: { pk: 'org_uuid' } },
  undefined,  // indexName
  true        // consistentRead
);

// GetItem with consistent read
await dynamoHelper.getItem(
  { pk: 'org_uuid', sk: 'product_xxx' },
  ['id', 'name'],
  true  // consistentRead
);

// BatchGetItems with consistent read
await dynamoHelper.batchGetItems(
  [
    { pk: 'org_uuid', sk: 'product_1' },
    { pk: 'org_uuid', sk: 'product_2' },
  ],
  ['id', 'name', 'price'],
  true  // consistentRead
);

Notes:

• Defaults to eventually consistent reads when not specified (backward compatible)
• Not supported on Global Secondary Indexes (AWS limitation)
• Consumes 2x read capacity units vs eventually consistent reads

Test Performance Fix:

Fixed a memory leak in queryWithCursor.spec.ts that was causing out-of-memory errors in CI/CD:

• The DynamoDBPaginateQueryMockImpl class was creating a new copy of 300 test items on every instantiation
• Tests making multiple paginated calls (e.g., 30 calls) created ~9,000 item copies in memory
• Solution: Reuse mock instances with a reset() method instead of creating new ones
• Impact: Reduced memory usage and improved test execution time by ~28% (4.6s → 3.3s)

Related Issues

Issue: #173

How Has This Been Tested

• Added 12 test cases covering consistentRead: true, false, and undefined for all four functions
• Verified parameter is only included in AWS SDK call when explicitly set
• All 124 tests pass with 94.81% statement coverage
• Tested chunked requests in batchGetItems (>100 items) to ensure consistent read is applied across all batches
• Fixed memory leak in test suite - tests now run without out-of-memory errors
• Test execution time improved from ~4.6s to ~3.3s

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

Screenshots (if appropriate)

N/A

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Support Consisent Read in Get/Query operations</issue_title>
<issue_description>User Story
Support consistent read operations using ConsistentRead as true.

https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_GetItem.html
https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html
https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_Query.html

Acceptance Criteria
Write acceptance criteria for this user story to be completed.

Additional context
Add any other context or screenshots about the feature request here.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Support Consisent Read in Get/Query operations #173

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[snehithv]

@copilot fix the unit test as the current failing one always runs out of memory

[Copilot]

@copilot fix the unit test as the current failing one always runs out of memory

Fixed the memory leak in queryWithCursor.spec.ts. The mock implementation was creating a new copy of 300 test items on every instantiation, causing memory issues when tests made multiple calls (e.g., 30 calls = 9,000 item copies).

Changed to reuse mock instances with a reset() method instead of creating new ones. This reduced memory usage and improved test execution time by ~28% (4.6s → 3.3s).

Commit: eab7090