Update Existing PR workflow often runs into merge conflicts

Since the update workflow edits the commonly updated default.config/*component.json files it almost always ends up in a conflict. We'd need to determine a way of auto-resolving conflicts, probably always prefer changes from the PR. This is needed to truly make this an automated process. Any thoughts on this are welcome.

Start with the Update Existing PR workflow and inspect how it edits the default.config/*component.json files and handles merge conflicts. Determine whether conflicts can be resolved automatically by preferring changes from the PR; done means the workflow completes without manual conflict resolution for these updates.

Written by the indexing model from the issue text.