test_psa_compliance.py is now in the framework, so shared between mbedtls-3.6, development (in TF-PSA-Crypto) and any future LTS. Right now this is ok because TF-PSA-Crypto hasn't progressed past 3.6 in terms of compliance, but over time the branches will diverge.

The goal of this task is to split the bulk of the code of test_psa_compliance.py which remains in the framework, from the branch-specific data which should be kept in each consuming branch. The branch-specific data is:

• EXPECTED_FAILURES
• PSA_ARCH_TESTS_REF

I suggest we use the same architecture as for analyze_outcomes.py: almost all the code is in a non-executable module in the framework, and there is a very simple script in each consuming branch that defines the data and calls framework_module.main(data).