One way to achieve that is to ask Dependantbot to submit a PR updating the lockfiles and automerge it later if CI passes. But as we are building the images for multiple stream, this would result with multiple PRs that will be open everyday, hence increasing the churn.

Another way is to realize those operations but in a forked repo, onboarded on Konflux as well. And then add another GH action to push the commits updating the lock files directly to the main repo, reducing the churn in the main repo. Note that the opened PRs in fork repo won't be merged, but the commit will be push fast-forward directly to the main repo, and then the PR will be closed.

DoD: the lock files are updated daily with minimal human interaction.