DbtCLI fails if profiles.yaml exists in the root directory and user provides a different profile in the task properties

[anna-geller]

Expected Behavior

If the user provides a different profiles in the profiles property of the DbtCLI task, we should simply overwrite the one in the working directory with the one specified on the task. Currently the task simply fails if a profiles.yaml file already exists instead of overwriting it

Actual Behaviour

No response

Steps To Reproduce

No response

Environment Information

• Kestra Version:
• Plugin version:
• Operating System (OS / Docker / Kubernetes):
• Java Version (If not docker):

Example flow

No response