Add Support for IonElement

[zihaowang678]

Summary
This PR adds support for the ION_ELEMENT_DOM API to the ion-java-benchmark-cli, enabling benchmarking of the IonElement library from ion-element-kotlin alongside the existing STREAMING and DOM APIs.

Changes

1. API Enum Enhancement (API.java)

• Added ION_ELEMENT_DOM enum value with documentation

2. Read Task Implementation (IonMeasurableReadTask.java)

• Implemented element reading methods for buffer and file operations
• Added proper resource management and side effect consumer integration

3. Write Task Implementation (IonMeasurableWriteTask.java)

• Added generateWriteInstructionsElement() method
• Integrated element processing with limits and flush period support

4. Task Routing (MeasurableReadTask.java & MeasurableWriteTask.java)

• Added ION_ELEMENT_DOM routing in getTask() and setUpTrial() methods

5. CLI Documentation (Main.java)

• Updated --api option to include ion_element_dom with format restrictions

6. Dependencies (pom.xml)

• Added ion-element (1.3.0) and Kotlin dependencies

7. Test Coverage (OptionsTest.java)

• Added comprehensive tests for read/write operations with various configurations

Performance Analysis
Evaluated on three Ion corpus datasets, including both Ion text and Ion binary data, IonElement shows an average of ~37.09% increase in primary_score of performance compared to IonValue.

[popematt]

I have a few questions and suggestions, but overall this is looking pretty good.

[popematt]

Just curious—when you run this, what sort of results to you get?

[zihaowang678]

It runs two APIs in sequence, then gives two stacked statistical summaries at the end, one for each API.

[popematt]

Sorry, I should have been more clear. Approximately how much of a performance difference are you getting between the two APIs when you run this command?

[zihaowang678]

Approximately a 30-ish percentage improvement in primary_score. While this command is a rough comparison between two APIs, the result aligns well with our more extensive experiments run in SampleTime mode across three ion datasets, where we saw a ~37.09% improvement in primary_score.

[popematt]

Not a blocker—it would be nice if we could add new APIs to the benchmark CLI without having to add more methods for each one. (Especially since they are unlikely to be applicable for all data formats.) Have you thought about any ways this could be factored to make it more easily extensible?

[zihaowang678]

You're right, the current approach is a straightforward one but doesn't scale well. A capability-based system where each format declares which APIs it supports might be better. I'd be happy to refactor this in a follow-up if it's worth doing.

[tgregg]

It's looking good! Note the failing CI build.

[tgregg]

I'm excited to be able to use this to make the case for adoption of ion-element-kotlin over IonValue.

Once @popematt approves, we can squash/merge.