fix: failing tests on RemoteConsoleIT, RemoteGremlinIT, JsFunctionsTest

[robfrank]

Summary

Fixes four failing tests on the current branch:

• RemoteConsoleIT.projectionOrder - RemoteDatabase.json2Result used a HashMap in the per-column type-hint branch added by Query count(*) return different field type depending on whether RemoteDatabase or RemoteGrpcDatabase is used. #4267, which silently reshuffled SELECT projection column order over the HTTP wire. Swap to LinkedHashMap to match the pre-Query count(*) return different field type depending on whether RemoteDatabase or RemoteGrpcDatabase is used. #4267 behavior of result.toMap() (which already returned a LinkedHashMap from JSONObject.toMap()).
• RemoteGremlinIT / RemoteGremlinFactoryIT - assertion type updated from Integer to Long to match the now-correct numeric type returned by remote count queries (Query count(*) return different field type depending on whether RemoteDatabase or RemoteGrpcDatabase is used. #4267 follow-up).
• JsFunctionsTest.objectComparison - test JS function now parses its JSON parameter; SQL invocation corrected.

Test plan

• mvn test -pl console -Dtest=RemoteConsoleIT - 16/16 pass
• mvn test -pl server -Dtest='Issue4267CountTypeIT' - 2/2 pass (verifies the original Query count(*) return different field type depending on whether RemoteDatabase or RemoteGrpcDatabase is used. #4267 fix still works)
• CI runs the gremlin and e2e suites

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 20 complexity

Metric	Results
Complexity	20

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[gemini-code-assist]

Code Review

This pull request updates JS and Gremlin tests to fix syntax and type assertions, and switches a HashMap to a LinkedHashMap in RemoteDatabase.java to preserve insertion order. Feedback has been provided regarding an extra leading space inside an assertThat call in RemoteGremlinFactoryIT.java and an optimization for initializing the LinkedHashMap capacity in RemoteDatabase.java to prevent unnecessary rehashing.

[gemini-code-assist]

There is an extra leading space inside the assertThat method call. According to the Google Java Style Guide, horizontal whitespace should not appear immediately after an opening parenthesis.

Suggested change

	assertThat( list.nextIfAvailable().<Long>getProperty("result")).isEqualTo(1_000);
	assertThat(list.nextIfAvailable().<Long>getProperty("result")).isEqualTo(1_000);

References

1. Google Java Style Guide: No whitespace should be added after the opening parenthesis of a method call. ^(link)

[gemini-code-assist]

When initializing a LinkedHashMap with a known size, it is recommended to calculate the initial capacity taking the default load factor (0.75) into account to avoid unnecessary rehashing/resizing when the map is populated.

Suggested change

	final Map<String, Object> converted = new LinkedHashMap<>(map.size());
	final Map<String, Object> converted = new LinkedHashMap<>((int) Math.ceil(map.size() / 0.75f));