Move Go Tip installation into sub-action

[yurishkuro]

Which problem is this PR solving?

• Unit tests on Go Tip sometimes fail because Go Tip fails to install, but the output is non-descriptive, e.g. https://github.com/jaegertracing/jaeger/actions/runs/7263410887/job/19788655227

Description of the changes

• Move Go Tip installation into a separate sub-action
• Add some debug logging to see the progress to make it easier to debug in case of failures (right now it's hard to tell which step is actually failing and resulting in the errors above)

How was this change tested?

• Tested in personal repo: https://github.com/yurishkuro/test-project-3/actions/runs/7264047725/job/19790690846

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (09080e6) 95.60% compared to head (f020c6a) 95.60%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5020   +/-   ##
=======================================
  Coverage   95.60%   95.60%           
=======================================
  Files         319      319           
  Lines       18786    18786           
=======================================
  Hits        17960    17960           
  Misses        663      663           
  Partials      163      163           

Flag	Coverage Δ
cassandra-3.x	25.63% <ø> (ø)
cassandra-4.x	25.63% <ø> (ø)
elasticsearch-5.x	19.89% <ø> (ø)
elasticsearch-6.x	19.89% <ø> (-0.02%)	⬇️
elasticsearch-7.x	20.04% <ø> (+0.01%)	⬆️
elasticsearch-8.x	20.13% <ø> (ø)
grpc-badger	19.52% <ø> (ø)
kafka	14.12% <ø> (ø)
opensearch-1.x	20.04% <ø> (ø)
opensearch-2.x	20.04% <ø> (+0.01%)	⬆️
unittests	93.34% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jkowall]

lgtm!

[yurishkuro]

And, by coincidence, the build just failed with this change, and I was even able to reproduce:

$ curl -fsSL https://storage.googleapis.com/go-build-snap/go/linux-amd64/03242506def60494d1b7231e2be57ea2f07f27a8.tar.gz -o gotip.tar.gz
curl: (22) The requested URL returned error: 404

Note that while I was testing the change a few minutes ago the HEAD commit of Go was 52dbffeac86863e1e0c9455b5b216ec50c828946. So it is possible we have a race condition between new commit showing on HEAD and the build becoming available from go-build-snap

4min later it's there. Maybe we could have some retry loop in the action.