refactor(loader): prepare JVM tests and resource for Java17

[imbajin]

Purpose of the PR

Loader test tooling needs JVM compatibility preparation, and cleanup can leave its distinct clients open when failure-log or progress handling throws. Close both clients while preserving the primary exception, suppressed failures and input-progress semantics.

Original preparation and review: hugegraph#43.

Depends on #775. Merge the shared build preparation first. This PR targets master and currently includes prerequisite changes; after the prerequisite lands, rebase this same organization branch onto the updated upstream base and revalidate the module diff before merging.

Main Changes

• Inherit shared coverage tooling and include existing unit tests in the suite.
• Close both distinct clients on logger/progress failures without saving progress after a logger failure or repeating close side effects.
• Preserve test profile selection and add the scoped JVM opening required by Hive ORC.
• Honor JAVA_HOME in launcher/converter paths and quote the selected Java executable; source/target remain Java 8.

Verifying these changes

• Trivial rework / code cleanup without any test coverage.
• Already covered by Loader unit tests and launcher checks.
• Need tests and can be verified as follows:
  • Preparation suites and profile models were validated on JDK 11 and 17.
  • Latest logger/progress failure, suppressed-error and idempotence regressions passed on native Java 17.
  • Previous file-profile validation covers ORC, Parquet, authentication and HTTPS; current-head CI is still running/queued.

Does this PR potentially affect the following parts?

• Nope
• Dependencies (build/test tooling only; runtime payload is unchanged by this preparation)
• Modify configurations (CI/test configuration)
• The public API (compatible behavior; signatures unchanged)
• Other affects: tests and validation tooling

Documentation Status

• Doc - TODO
• Doc - Done
• Doc - No Need

[codecov]

Codecov Report

❌ Patch coverage is 72.22222% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 52.27%. Comparing base (b066b80) to head (7c1ca96).
⚠️ Report is 246 commits behind head on master.

Files with missing lines	Patch %	Lines
.../apache/hugegraph/loader/executor/LoadOptions.java	0.00%	2 Missing and 1 partial ⚠️
.../apache/hugegraph/loader/executor/LoadContext.java	86.66%	2 Missing ⚠️

❗ There is a different number of reports uploaded between BASE (b066b80) and HEAD (7c1ca96). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (b066b80)	HEAD (7c1ca96)
	2	1

Additional details and impacted files

@@              Coverage Diff              @@
##             master     #778       +/-   ##
=============================================
- Coverage     62.49%   52.27%   -10.23%     
+ Complexity     1903      986      -917     
=============================================
  Files           262      111      -151     
  Lines          9541     5875     -3666     
  Branches        886      755      -131     
=============================================
- Hits           5963     3071     -2892     
+ Misses         3190     2561      -629     
+ Partials        388      243      -145     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bitflicker64]

Blocking: no. Summary: The LoadContext cleanup now closes both distinct clients with the primary exception preserved, and the CLI exit codes are fixed; the new unit tests run in loader CI (UnitTestSuite 33 tests passing). One Minor launcher diagnosability regression. Score 8/10. Evidence: exact-head worktree review of the full diff, LoadContext/LoadOptions call sites, loader-ci (11) job log, and a local reproduction of the launcher exit path under set -eo pipefail.