[CI] UpdateCLI: Added go mod tidy

[pazone]

Proposed commit message

Performs go mod tidy after updating the go version in go.mod

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[v1v]

Will this cause any issues if the golang-bump happens afterwards? Let's say current version is 1.22.7 and the upcoming one is 1.22.8, hence this step will point to 1.22.7 but the updatecli pipeline will move the version from 1.22.7 to 1.22.8

[pazone]

Good question. It's better to install the new version of go.

[v1v]

Hence, this change will not install the new version if that's the pre-req

[pazone]

Updatecli can neither execute a specified target nor run a subset of targets. I came up with one solution that I don't like.

1. run updatecli with --commit false --push false. It applies the changes to the target files.
2. install go with GHA using updated .go-version
3. run updatecli again without --commit false --push false and it pushes the changes.

Please check the updates. Do you have any ideas on how can we make it in one execution?

[v1v]

First, can you explain the motivation for running go mod tidy? I have not seen the need to use it while running the same mechanism with other golang versions:

• [Automation] Bump Golang version to 1.22.7 #41018
• [Automation] Bump Golang version to 1.22.6 #40528
• [Automation] Bump Golang version to 1.21.12 #40114

Updatecli can neither execute a specified target nor run a subset of targets.

As far as I see there is a parameter called dependson, see https://www.updatecli.io/docs/core/target/#_parameters:

"dependson" allows to specify the order of execution of resources It accepts a list of rules like "(resourceType#)resourceId(:booleanOperator)" The resourceType is optional and can be one of "condition", "source" or "target"

[v1v]

Will this change also needed in bump-golang-7.17.yml?

[pazone]

Added the same for 7.17

[v1v]

ditto