chore: enable test.multi-node test during pr and nightly build.

[He-Pin]

Motivation:
refs: #1591

Need to make sure MultiJvm/test pass.

I was running MultiJvm/test code locally.

[He-Pin]

Enabling MultiJvm/test in PR and nightly builds is important for catching cluster-related regressions early.

1. CI impact: Multi-node tests are expensive and slow. Are there concerns about CI duration? The change appears minimal (just toggling flags in workflow files).

2. Flakiness risk: Multi-node tests can be flaky, especially in CI environments. Has the author verified these tests pass reliably on CI?

3. Staleness: Open since December 2024 with no reviews. @He-Pin mentioned running MultiJvm tests locally. It would be good to see CI results before merging. If the tests are stable, this is a straightforward and valuable improvement.

[He-Pin]

Closing due to staleness and merge conflicts. Enabling multi-node tests in PR/nightly builds is a significant CI decision that needs team discussion around test duration and flakiness tradeoffs. If there is consensus to proceed, a fresh PR with that discussion can be opened.