Refactor table policy updates to use a class that can be extended

[Will-Lo]

Summary

Issue] Briefly discuss the summary of the changes made in this
pull request in 2-3 lines.

Table policies are currently always written to table properties when updated.
In scenarios where we want this behavior to change for specific policies (e.g. Retention) this is not easy to extend in another class.

This PR refactors the writing and comparison of policies into its own class so that it is possible to change the behavior of storing table policies.

To manage policies at a granular level, incoming policies can be read through TableDto and modifying the policy object to store only the policies that should be saved.

Changes

• Client-facing API Changes
• Internal API Changes
• Bug Fixes
• New Features
• Performance Improvements
• Code Style
• Refactoring
• Documentation
• Tests

For all the boxes checked, please include additional details of the changes made in this pull request.

Testing Done

• Manually Tested on local docker setup. Please include commands ran, and their output.
• Added new tests for the changes made.
• Updated existing tests to reflect the changes made.
• No tests added or updated. Please explain why. If unsure, please feel free to ask for help.
• Some other form of testing like staging or soak time in production. Please explain.

For all the boxes checked, include a detailed description of the testing done for the changes made in this pull request.

Additional Information

• Breaking Changes
• Deprecations
• Large PR broken into smaller PRs, and PR plan linked in the description.

For all the boxes checked, include additional details of the changes made in this pull request.