Make publishing tests run in repeatable order

Required prerequisites

[x] Consult the security policy. If reporting a security vulnerability, do not report the bug using this form. Use the process described in the policy to report the issue.
[x] Make sure you've read the documentation. Your issue may be addressed there.
[x] Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
[ ] If possible, make a PR with a failing test to give us a starting point to work on!

Describe the bug

Our Publishing pipeline is not running tests in a repeatable order, which can cause non-repeatable behavior.

For example, one can compare the logs from the following runs

The Testing photonics: line appears later in the other run.

Non-repeatable behavior is just a nuisance sometimes, but it can also apparently cause some of our Python notebooks to fail if all the dependencies aren't correct.

The root cause is likely all of the find commands in validate_container.sh. E.g. https://github.com/NVIDIA/cuda-quantum/blob/735e62b27a2f534278b225e53453ad131b1cbf0b/scripts/validate_container.sh#L130. The find command returns results in a non-deterministic order (depending on how all the files were created), so its outputs likely need to be piped to sort to achieve a repeatable behavior.

Steps to reproduce the bug

See above.

Expected behavior

The publishing pipeline needs to run tests in repeatable order.

Is this a regression? If it is, put the last known working version (or commit) here.

Not a regression

Environment

CUDA Quantum version: latest (735e62b27 as of now)
Python version:
C++ compiler:
Operating system:

Suggestions

No response

NVIDIA / cuda-quantum