chore: upgrade the project version to 1.8.0

[imbajin]

Purpose of the PR

Build and report HugeGraph 1.8.0 instead of 1.7.0. Preserve Java 17, Commons/RPC Java 11 bytecode, independent REST protocol versions and the current TinkerPop adaptation.

Published download links, image tags and README version badges stay on available releases. TODOs mark their post-release update; this PR does not publish artifacts or images.

Main Changes

• Align revision, VersionInBash and filtered resources to 1.8.0; inherit the Commons revision. Reuse master’s existing parent-POM flattening and Cluster Commons dependency management.
• Keep Toolchain Client 1.5.0 independent. Declare Commons directly on the cluster test leaf so Maven -am builds it locally; inherit its version from master’s dependency management and retain master’s refreshed legal inventory.
• Keep Helm Chart 0.1.1 with appVersion/latest images until 1.8.0 images are published. Align label snapshots and empty-tag tests; preserve explicit tag/digest overrides and independent Hubble selection.
• Remove retired Memory and Commons Java 11 alias checks; retain actual Memory suites, the always-reported summary and the two required contexts (check-license, Server memory tests).
• Align the Javassist inventory/license entries with the runtime dependency scan.
• Correct the Struct staging switch, select known CI maintenance and Docker version inputs precisely, and limit Commons installation to Common/RPC and upstream POMs.
• Reuse existing graph write/read/Gremlin smoke for both current PR image topologies; add history-based PD/Store/Commons/Cluster timeout budgets. Run the lightweight TP branch/report checker from PD/Store CI even when Server tests are not selected.
• Record the actual PR merge base when master advances; verify the event merge SHA and unchanged PR head instead of requiring an outdated event base.
• Check exact product, Gremlin and independent API versions in existing smoke checks.
• Repair the existing RPC random-routing test: accept valid repeated provider selection, preserve deterministic balancing assertions, and clean local clients/servers even after assertion failure. Production RPC code is unchanged.

Verifying these changes

Changes originate in Org PR #275 and use the same branch and commits here.

• Java 17 root formatting/clean compilation and Commons/RPC suite checks pass after integrating master, with Commons tests explicitly enabled.
• Helm lint and rendering checks pass for empty tags, latest labels and explicit tag/digest overrides. Shell syntax and changed-line checks pass.
• Before the master update, the Maven/version changes were validated with an isolated external consumer for common, rpc, core, Struct and PD/Store clients, without source mounts or revision overrides. Filtered resources, JAR metadata and Java 11/17 bytecode boundaries were checked.
• CT leaf compilation and dependency-tree checks pass without preinstalled HugeGraph artifacts; the selected reactor includes Commons 1.8.0.
• CI selection, deployment checker, TP branch/report and dependency inventory checks pass; YAML checks confirm real Memory jobs, triggers and required contexts are preserved.
• Current-commit CI passes in both Org and ASF: Memory/RocksDB/HBase, PD/Store/HStore, Cluster, Commons/RPC, both macOS architectures, RISC-V, current-image graph write/read smoke, Helm, CodeQL and dependency checks. Codecov is excluded from acceptance as agreed.

Dependency Review passes on the current commit without lowering security thresholds, exempting vulnerabilities or upgrading Spring. The related snapshot/security investigation is tracked in Issue #3283.

TinkerPop suites remain limited to release-, test- and tinkerpop- branches. Remove obsolete task-branch conditions and the temporary skip; this version-only upgrade branch does not run long TP suites. Broader CI changes are recorded in docs/ci.md for follow-up. Toolchain source changes, downstream qualification, full migration/rollback and formal release are outside this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 37.51%. Comparing base (7398075) to head (8184f01).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #3282      +/-   ##
============================================
- Coverage     41.18%   37.51%   -3.67%     
+ Complexity     6771     4878    -1893     
============================================
  Files           766      573     -193     
  Lines         66086    53125   -12961     
  Branches       8773     7250    -1523     
============================================
- Hits          27218    19932    -7286     
+ Misses        35819    30899    -4920     
+ Partials       3049     2294     -755     

☔ 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.

[bitflicker64]

Blocking: yes. Summary: The Maven revision, VersionInBash, the root flatten plugin and the exact-version smoke checks line up and pass in CI. Setting the Helm appVersion to 1.8.0 before any 1.8.0 image exists means an empty image tag now renders an image reference that cannot be pulled, and every pod gets a 1.8.0 version label while it runs latest. Two smaller gaps: license files for the two removed jars stay in the release docs, and several 1.7.0 references outside the files you marked have no post-release TODO. Evidence: full diff of 5854beb against merge-base d9abcd4 (18 files, 6 commits). _helpers.tpl:1001 renders default .appVersion $img.tag, and the PR's own image_digest_test.yaml asserts hugegraph/pd:1.8.0 for an empty tag. Docker Hub returns 404 for hugegraph/{pd,store,server}:1.8.0 and 200 for 1.7.0. git grep at the head for 1.7.0 and for the removed jar names. Hard-coded version consumers (CoreVersion, CommonVersion, RpcVersion, ApiVersion) read version.properties or the manifest. The /versions checks ran and passed in docker-build and build-server-riscv64. Latest-head CI is not green: affected-module-tests fails because commons / Commons tests (Java 17) failed in hugegraph-rpc ServerClientTest (bind failed, address already in use; this looks like a flaky port clash rather than this diff), and the advisory dependency-review flags spring-webmvc 5.3.27 in hg-pd-dist (critical). That looks pre-existing and shows up only because the base has no dependency snapshot.