Copier updates with merge conflicts should fail renovate/artifacts check

[rarkins]

Discussed in #31592

^{Originally posted by PJ-Schulz September 25, 2024}

Tell us more.

A merge conflict can occur during a copier update if a manual change has been made between two versions. I have reproduced this behavior in an example repository. This is the PR Renovate creates: PJ-Schulz/my-renovate-test#3

In this snipped you can see the example merge conflict:

      containers:
      - name: my-app
<<<<<<< before updating
        image: nginx:alpine
=======
        image: nginx:1.27.1
>>>>>>> after updating
        resources:
          limits:

Currently Renovate only writes a comment in the Pull Request. In my opinion, it would be better if there was an artifact update error and the update was interpreted as failed. This way a person can manually resolve the conflict.