Support READ-COMMITTED isolation

[brfrn169]

Description

This PR adds support for the READ-COMMITTED isolation introduced by scalar-labs/scalardb#2803.

Related issues and/or PRs

• Add READ_COMMITTED isolation scalardb#2803

Changes made

• Fixed the validation for the isolation level.
• Added a string conversion for the isolation level.

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)

N/A

[Copilot]

Pull Request Overview

This PR extends the CLI runner to accept a new READ-COMMITTED isolation level, updating validation logic accordingly.

• Added :read-committed to the allowed isolation levels
• Updated the validation error message to list the new option

Comments suppressed due to low confidence (2)

scalardb/src/scalardb/runner.clj:118

• Consider updating the user-facing documentation or README to mention the new read-committed option so that users see the supported isolation levels in all usage guides.

    :validate [#{:read-committed :snapshot :serializable}

scalardb/src/scalardb/runner.clj:118

• There are no existing tests covering the read-committed isolation level for the CLI runner; adding a unit or integration test will ensure this new option is recognized and handled correctly.

    :validate [#{:read-committed :snapshot :serializable}

[yito88]

LGTM!

[feeblefakie]

LGTM! Thank you!