revert: (dynamodb) revert Table.table field to private to fix .NET naming

[pahud]

Issue # (if applicable)

Closes #36025.

Reason for this change

The Table class in aws-dynamodb was incorrectly renamed to Table_ in .NET bindings starting from v2.222.0, breaking all .NET CDK applications using DynamoDB tables. This regression was introduced in PR #35554 when the internal table field was changed from private to protected, creating a JSII naming conflict in .NET where property names cannot match class names.

Description of changes

This PR reverts the table field visibility from protected back to private at line 1213 in packages/aws-cdk-lib/aws-dynamodb/lib/table.ts.

Technical details:

• Changed protected readonly table: CfnTable; to private readonly table: CfnTable;
• This is a single-line change that resolves the JSII naming conflict
• The field is only used internally within the Table class (7 internal usages verified)
• No subclasses of Table exist in the codebase
• JSII compilation now succeeds without renaming the Table class in .NET

Impact:

• Fixes .NET class name from Table_ back to Table
• Restores v2.221.1 behavior
• No impact on TypeScript, Python, Java, or Go bindings
• No functional or API changes
• Better encapsulation by keeping internal implementation details private

Description of how you validated changes

• Unit tests: All 348 existing unit tests in aws-dynamodb pass without modification
  • Test suites: 6 passed
  • Tests: 348 passed, 0 failed
• Build validation:
  • TypeScript compilation: SUCCESS
• JSII verification: Confirmed no JSII warnings for Table class in build output, indicating .NET bindings will use correct class name

 % npx lerna run build --scope=aws-cdk-lib --skip-nx-cache
 2>&1 | grep -i "table" | grep -i "warning\|conflict\|rename"

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[ozelalisen]

@Mergifyio requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.