Refactor update golang dependencies workflow

Currently, we have both updatecli and dependabot to update Go dependencies, which leads to confusion.

We need to refactor our workflows, keep only one that updates the dependencies (except for beats that will be covered in a separate workflow).

We need to choose between dependabot, updatecli, and renovate.

Some rules of thumb that we might need to consider:
* having a open pull request limit
* having well-organized of update groups (e.g. each cloud sdk is a group)
* optionally a functionality like dependabot's [cooldown](https://github.com/elastic/cloudbeat/issues/3651) option might be usefull to utilze.

Update: (add renovate / Renovate Scalability Project to comparison)