🧪 setup_codes: start from a clean profile (aiidateam#7600)

The fixture builds three codes whose labels collide with the first one's
pk and uuid, which only tests ambiguity resolution if no other codes are
present. It took whatever the session profile held.

That includes a computer imported from an archive by an earlier test in
the same worker, labelled `localhost` but carrying the pre-2.0 transport
name `local`, which `aiida_localhost` cannot match and cannot recover
from once the unique label collides. Every test here then errors during
setup.

Author: GeigerJ2

tests/cmdline/params/types/test_code.py

@@ -25,7 +25,7 @@ def parameter_type():
 
 
 @pytest.fixture
-def setup_codes(aiida_localhost):
+def setup_codes(aiida_profile_clean, aiida_localhost):
     """Create some `Code` instances to test the `CodeParamType` parameter type for the command line infrastructure.
 
     We create an initial code with a random name and then on purpose create two code with a name that matches exactly