test: make adapter YAML-parity assertion order-independent

test_fallback_precedence_and_yaml_parity compared discover_adapters()
output (filesystem scan order, varies by OS/filesystem) against the YAML
manifest order as an ordered list, so it failed on some runners. Parity
means the same set of adapters, not the same order — compare sorted.

Signed-off-by: aviv ron <rona@il.ibm.com>

Author: aviv1ron1

tests/composer/test_adapter_loader.py

@@ -541,6 +541,9 @@ def test_fallback_precedence_and_yaml_parity(self, tmp_path):
 
         # Verification of Parity: compare (path, name, technology) - source differs by design
         # discover_adapters returns source=None, discover_adapters_from_yaml returns source=manifest_path
+        # Compare order-independently: discover_adapters walks the filesystem (scan
+        # order varies by OS/filesystem) while the YAML path follows manifest order,
+        # so parity means the same set of adapters, not the same ordering.
         adapters_without_source = [(p, n, t) for p, n, t, _ in adapters]
         yaml_without_source = [(p, n, t) for p, n, t, _ in yaml_adapters]
-        assert adapters_without_source == yaml_without_source
+        assert sorted(adapters_without_source) == sorted(yaml_without_source)