[Improve] add macOS Apple Silicon smoke test for Gremlin Console

[contrueCT]

Background

This follow-up task is related to issue #3006.

Issue #3006 reported that bin/gremlin-console.sh can fail on Mac M4 / Apple Silicon. However, the exact cause has not been fully isolated yet and should not be assumed in advance.

PR #3010 is intentionally focused on rerun CI behavior and macOS RocksDB server/API checks, so the Gremlin Console Apple Silicon validation is tracked separately in this follow-up task.

Related context:

• issue [Bug] README “Build from Source” instructions outdated. "gremlin-console.sh" fails on Mac M4 (Apple Silicon) #3006 tracks the user-facing problem around outdated build/startup docs and bin/gremlin-console.sh failures on Mac M4 / Apple Silicon
• PR chore(ci): optimize rerun workflow and add macOS RocksDB coverage #3010 adds macOS RocksDB CI coverage, but does not cover the bin/gremlin-console.sh entry point

Problem

bin/gremlin-console.sh is a different entry point from the HugeGraph server startup path and has its own runtime behavior on macOS Apple Silicon.

At the moment, this path is not covered by a dedicated macOS Apple Silicon smoke test in CI, which means regressions or platform-specific startup failures may not be detected early.

Proposal

Add a focused follow-up for Gremlin Console on macOS Apple Silicon, for example:

• add a lightweight macOS smoke test for bin/gremlin-console.sh
• validate a tiny non-interactive invocation such as:
  • gremlin-console.sh -- -e <script>
• investigate the actual startup/runtime failure mode on Apple Silicon

Expected Outcome

• CI can catch obvious regressions in the console startup path

[contrueCT]

I plan to follow up on this issue with a dedicated PR after PR #3010 is settled.