CI: use LTS container packages in test workflows

[Stardust0831]

Important

This PR depends on #7781 and must not be merged first.

Merge order:

1. Merge CI: isolate LTS container packages #7781 into LTS.
2. Wait for its Container workflow to publish and verify that abacus-gnu-lts:latest, abacus-intel-lts:latest, and abacus-cuda-lts:latest are pullable.
3. Rebase/update this PR, mark it ready for review, and merge it into LTS.

Reminder

• Have you linked an issue with this pull request?
• Have you added adequate unit tests and/or case tests for your pull request?
• Have you noticed possible changes of behavior below or in the linked issue?
• Have you explained the changes of codes in core modules of ESolver, HSolver, ElecState, Hamilt, Operator or Psi? (not applicable)

Linked Issue

Follow-up to #7781. Related to #7780.

Unit Tests and/or Case Tests for my changes

• Parsed all 10 changed workflow files with Ruby/Psych -- passed (10/10).
• Verified every ABACUS GHCR reference in the LTS workflows uses the -lts package namespace -- passed (13/13).
• git diff --check upstream/LTS...HEAD -- passed.
• Runtime Actions verification is intentionally blocked until CI: isolate LTS container packages #7781 publishes the three LTS images.

What's changed?

• Switch GNU, Intel, and CUDA container references in all LTS test workflows from the develop-owned abacus-* packages to abacus-*-lts.
• Cover Build Test, Makefile Build Test, integration/unit tests, PyTest, coverage, CUDA, dynamic, performance, and full/smoke toolchain workflows.
• Keep the unsuffixed abacus-*:latest packages owned by develop for backward compatibility with existing consumers.

This branch is stacked on #7781, so the PR currently also contains its publisher-isolation commit. Once #7781 is merged into LTS, only the test-consumer migration remains as the effective diff.

Any changes of core modules? (ignore if not applicable)

• None. This PR only changes LTS workflow container references.