HTS concurrent put and delete resolution -- Reopen and Refractor tests

[jiang95-dev]

Summary

Bug fix for the reverted pr. This PR refractors the fragile unit tests. The save() method will change the state of the hts storage, so we need to delete all instances after each test to prevent the state propagation. The save() method will also update the version of TEST_USER_TABLE_ROW from null to 0, and even the builder cannot change the version to null (reason still unknown). So we need to avoid using static TEST_USER_TABLE_ROW, but instead create an instance for each test.

Changes

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

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

Testing Done

• [x] Manually Tested on local docker setup. Please include commands ran, and their output.
• [x] Added new tests for the changes made.
• [x] 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.

[jiang95-dev]

Why did the pre-commit succeed but post-commit fail with the previous instance of the PR? could you capture those details in the description

The hypothesis is that pre-commit didn't capture the new commit. This is a common phenomenon of Github Action as I have encountered it several time.