Add tearDown method to LoRA tests.

[DN6]

What does this PR do?

Some LoRA tests do not have tearDown methods. It might explain some of the timeouts we're seeing in the CI. In any case the GPU related tests should always have tearDowns.

Fixes # (issue)

Before submitting

• This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• Did you read the contributor guideline?
• Did you read our philosophy doc (important for complex PRs)?
• Was this discussed/approved via a GitHub issue or the forum? Please add a link to it if that's the case.
• Did you make sure to update the documentation with your changes? Here are the
  documentation guidelines, and
  here are tips on formatting docstrings.
• Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

[sayakpaul]

Why this?

[DN6]

Fixed.

[sayakpaul]

Thanks!

Do the LoRA tests leak memory?

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[DN6]

@sayakpaul Not 100% certain, but it does seem like the timeout issue is more prevalent in the LoRA tests. So they might be leaking memory.