ci: run single-node smoke only and disable multinode (backport #6908)

[warku123]

What does this PR do?

Backport of #6908 to the release_v4.8.2.2 branch (CI configuration only, no production code changes):

• Switches the single-node integration CI to run only the smoke test subset (--clean --smoke instead of the full suite)
• Removes the multinode integration CI workflow entirely
• Renames the single-node workflow, job, steps, and report artifact from "Full" to "Smoke" to reflect the actual scope

Why are these changes required?

The CI fix merged into develop via #6908 never landed on the release_v4.8.2.2 branch, so PRs targeting this branch still run the full single-node suite and the multinode suite, which fail stably for reasons unrelated to PR code:

• The full single-node suite's hardened assertions don't match the fixture baked into the troninfra/troninfra-ci image, causing stable failures unrelated to PR code.
• Per the QA/integration-test team, the multinode suite (--all) is QA's own regression suite — complex, not recommended for our CI, and not maintained by QA for CI usage.
• The smoke suite is the concise core integration test path; QA guarantees it stays valid and effective in CI.

Gating PRs on the smoke subset restores a reliable, QA-backed CI signal on the release branch, identical to what develop already does.

This PR has been tested by:

• Manual Testing (the workflow files on release_v4.8.2.2 were byte-identical to the base of ci: run single-node smoke only and disable multinode #6908, so the backport applies exactly; the resulting integration-test-single-node.yml matches the post-merge version already green on develop. This PR's own CI run executes the smoke subset and serves as the live verification.)

Follow up

• Coordinate with QA if more integration coverage is needed — new cases should be added to the smoke suite

Extra details

No production code changes; CI configuration only. Base branch is release_v4.8.2.2.