Re-Configure renovate bot for devfile/registry

[thepetk]

Which area is this issue related to?

/area ci
/area registry

Issue Description

After our onboarding to konflux we are receiving a slightly bigger number of PRs opened by the konflux bot. We might want to configure the new bot in a way that brings less noise with new updates

Acceptance Criteria

• The old redhat renovate bot has been removed
• The konflux renovate bot follow the same configuration with the old bot

[thepetk]

Regarding the case that the new bot creates two PRs for the same image, I noticed it was coming from two different bots. Example:

• chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v9 registry#517
• chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v1-1733173511 registry#519

[michael-valdron]

Regarding the case that the new bot creates two PRs for the same image, I noticed it was coming from two different bots. Example:

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v9 registry#517](https://github.com/devfile/registry/pull/517)

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v1-1733173511 registry#519](https://github.com/devfile/registry/pull/519)

@thepetk First one is renovate bot, second one is Konflux bot

[thepetk]

Regarding the case that the new bot creates two PRs for the same image, I noticed it was coming from two different bots. Example:

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v9 registry#517](https://github.com/devfile/registry/pull/517)

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v1-1733173511 registry#519](https://github.com/devfile/registry/pull/519)

@thepetk First one is renovate bot, second one is Konflux bot

yeap exactly!

[michael-valdron]

Regarding the case that the new bot creates two PRs for the same image, I noticed it was coming from two different bots. Example:

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v9 registry#517](https://github.com/devfile/registry/pull/517)

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v1-1733173511 registry#519](https://github.com/devfile/registry/pull/519)

@thepetk First one is renovate bot, second one is Konflux bot

yeap exactly!

What's interesting is that the Konflux bot change seems more what I'd expect, the renovate bot one is trying to leap to a much higher version tag 🤔

[thepetk]

@michael-valdron I've also noticed duplicate PRs (one major and one minor update) for the same image:

• chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v9 registry#543
• chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v1-1734610342 registry#537

I feel the best approach here is to only allow max one PR open for each image

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 120 days.