Comment 1 for bug 2052752

I can reliably reproduce this failure to clean up credentials on my environment with this test:

```
murano_tempest_tests.tests.api.application_catalog.artifacts.test_repository.TestRepositorySanity.test_get_list_packages[id-2818aaa0-6613-4bd9-8abe-02713121357a,smoke]
```

Which I believe is found in git+https://opendev.org/openstack/murano-tempest-plugin.git@2.6.0

In my environment (2023.2/stable sunbeam), this test is skipped with a message:

```
{3} setUpClass (murano_tempest_tests.tests.api.application_catalog.artifacts.test_repository.TestRepositorySanity) ... SKIPPED: Murano is not using GLARE backend. Skipping GL
```

Every time I run tempest with this test, I see another file left in the /tmp/tempest-lock directory, such that after 4 runs, the directory looks like this:

```
root@tempest-k8s-0:/tmp/tempest-lock# grep -r .
533bd1b808f1c89a41790ccb98b31610:TestRepositorySanity
7b03fe17fc92437c7bb7dff60b8bf565:TestRepositorySanity
e5604fdc3b6b8200b13a1bfa6c4bf8fa:TestRepositorySanity
22a805d5d9f003ab3342b9af2401528a:TestRepositorySanity
```

These files accumulate regardless of whether other tests run in the same tempest run or not (eg. running with --regex smoke or running with --regex 'murano_tempest_tests..*artifacts.test_repository.TestRepositorySanity').

These lock files that aren't cleaned up accumulate, and eventually cause tempest to fail to allocate accounts for tests.