Helm Operator will try to apply multiple times when two of more releases have the same name

[ghost]

Describe the bug
If someone accidentally uses a helm release name twice. The helm operator will keep trying to apply the change back and forth between the two releases. This results in many releases and could take down someones app.

To Reproduce
Steps to reproduce the behaviour:

1. Create two different helm releases with different settings apart from the ReleaseName

Expected behavior
The operator should back off and fail when there are two of the same release names in the queue.

** Additional info
This happend on our test clusters where we don't require PRs. A PR would likely of avoided this as someone would of checked it, but I think the helm operator should have some logic to fail when this happens. I will attempt to fix this with a PR and just wanted to log this in case someone else is already working on the issue.

Additional context
Add any other context about the problem here, e.g

• Flux version: 1.12.2
• Helm Operator version: 0.9.1