Migrate dt4acc integration to pyaml-test-lattice and pin CS backends

[gupichon]

Summary

• Source the FODO_1GeV_6D lattice/config for the dt4acc integration pipeline from pyaml-test-lattice instead of a vendored copy under tests/integration/data/fodo_1gev_6d/, resolving --accelerator-setup-file/--lattice-file and the test fixtures through pyaml_test_lattice.configurations/lattices.
• Pin tango-pyaml@0.3.3 and pyaml-cs-oa@0.2.0 in dt4acc-integration.yml instead of tracking main unpinned — both tags predate the MultiAttribute regression that broke CI on PR Fix typing for _fill_device() methods #393.
• Deactivate test_chromaticity_measurement (same convention as the existing deactivated_test_orbit_correction): pyaml-test-lattice's current fixture has no BPMs/correctors or tuning tools yet.

Closes #394

Test plan

• Local end-to-end run against a natively-launched dt4acc-soleil-twin (no WSL/Apptainer): both tango-pyaml and pyaml-cs-oa smoke tests pass.
• Full non-integration suite (pytest tests -m "not integration") unaffected.
• CI dt4acc-integration.yml run on this PR (Apptainer path).

[gupichon]

Maybe we should tag tango-pyaml and release it? @TeresiaOlsson ?

[JeanLucPons]

And pyaml-cs-oa too ?
There was also a recent fix.

[TeresiaOlsson]

Maybe we should tag tango-pyaml and release it? @TeresiaOlsson ?

Yes, I would like that also so I can see that the documentation builds correctly for what readthedocs calls stable. Currently it only build latest.

[TeresiaOlsson]

And pyaml-cs-oa too ? There was also a recent fix.

And maybe also pyaml? We can make pre-release tags if we are afraid of breaking things for users. But I think it would be good to make a release of all the packages this week so we have some days to fix potential bugs before the hackathon.