Ensure we create the secrets at the right time

What does this MR do?

In deploy, if the previous deployment failed, we delete/cleanup all the objects related to the release, including secrets. The problem is that if we create the root password before that, it will be then recreated during the deploy with a random value!

By creating the secret just before actually deploying a new release, we ensure that it won't be overridden.

What are the relevant issue numbers?

Closes #53621 (closed).

Does this MR meet the acceptance criteria?

• [-] Changelog entry added, if necessary
• [-] Documentation created/updated
• [-] Tests added for this feature/bug
• Conforms to the code review guidelines
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• [-] Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process.