Refactoring CoordinatorGroupCommitKeyManipulator by moving the implementation to DefaultGroupCommitKeyManipulator to improve the reusability

[komamitsu]

Description

In the current implementation, CoordinatorGroupCommitKeyManipulator designed to manipulate GroupCommit keys that are all String. But, the functionality should be reusable in other use cases, not only for the Coordinator Group Commit feature. This PR moves the implementation of CoordinatorGroupCommitKeyManipulator to DefaultGroupCommitKeyManipulator to make the functionality easier to reuse.

Related issues and/or PRs

• https://github.com/scalar-labs/scalardb-cluster/pull/834

Changes made

• Move the implementation of CoordinatorGroupCommitKeyManipulator to DefaultGroupCommitKeyManipulator. CoordinatorGroupCommitKeyManipulator inherits DefaultGroupCommitKeyManipulator now.
• Rename interface KeyManipulator to GroupCommitKeyManipulator to clarify what kind of keys the interface manipulate.

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• Tests (unit, integration, etc.) have been added for the changes.
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

This changes addresses this issue.

Release notes

N/A

[Torch3333]

LGTM, thank you!

[brfrn169]

LGTM! Thank you!

[feeblefakie]

LGTM! Thank you!