Add MIPS32 cross compilation, refactor existing cross-compilation jobs

[sirknightj]

Issue #, if available: N/A

What was changed?

• Updated the GitHub Actions CI configuration to include cross-compilation for mips-32, arm-32, arm-64, and aarch-64 targets, using the public.ecr.aws/ubuntu/ubuntu:22.04_stable Docker image for each cross-compilation environment.
• Removed previous individual cross-compilation jobs for arm64, linux-aarch64, and arm32, consolidating the builds into a unified matrix approach.

Why was it changed?

• Using the docker images should stop the builds from breaking randomly due to updates to GitHub actions runner images.
• Enable cross-compilation for additional architectures (mips-32) in the CI pipeline while ensuring a cleaner, more maintainable configuration.
• Removed redundant individual job definitions (arm-32, arm-64, aarch-64) and consolidated them into the matrix strategy to streamline the CI process.

How was it changed?

• Added new cross-compilation matrix in the CI configuration.
• For each architecture, defined specific cross-compilation toolchains, install dependencies, and adjusted flags to match the respective target platform (e.g., OpenSSL or MbedTLS).
• Integrated the public.ecr.aws/ubuntu/ubuntu:22.04_stable Docker image for containerized cross-compilation.
• Use file-expected-output parameter for each architecture to correctly match the generated output file.

What testing was done for the changes?

• Ran the new job on a fork of the repository and these changes succeed there.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[stefankiesz]

(nit) "Using CC: $CC and CXX: $CXX"

[stefankiesz]

Can you test that the CI job does fail if the build is successful but the files are missing or don't contain expected output?