updatecli(golang): use golang-crossbuild

[v1v]

Motivation/summary

7.17 uses https://github.com/elastic/golang-crossbuild

elastic/golang-crossbuild#420 was not merged therefore the packaging pipeline failed.

I added the feature branch in the name of the updatecli pipeline to help with creating a branch staring with feature/ in the upstream, then the buidlkite pipeline should be triggered automatically, see

apm-server/catalog-info.yaml

Line 44 in 4400426

filter_condition: build.branch == "main" || build.branch =~ /^[0-9]+\.[0-9]+$$/ || build.branch =~ /^feature\//

Checklist

• Update CHANGELOG.asciidoc
• Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

Related issues

[endorama]

Approving to unblock but I'd like a clarification:

elastic/golang-crossbuild#420 was not merged therefore the packaging pipeline failed.

What's the relation between that go update and the failing build? Is it due to the 1.21.12 specified in .go-version?

[v1v]

Is it due to the 1.21.12 specified in .go-version?

That's correct