utils/build/docker/golang/app: update app for v2 API changes

[knusbaum]

Motivation

Changes

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• Relevant label (run-parametric-scenario, run-profiling-scenario...) are presents
• No system-tests internal is modified. Otherwise, I have the approval from R&P team
• CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
• A docker base image is modified?
  • the relevant build-XXX-image label is present
  • To R&P team: locally build and push the image to hub.docker.com
• A scenario is added (or removed)?
  • Get a review from R&P team
  • Once merged, add (or remove) it in system-test-dasboard nightly

[robertomonteromiguel]

I guess We can change the status of this PR to Draft

[darccio]

Oops, fixing.

[darccio]

@knusbaum I accidently merged main into this PR. I reverted that and recovered your changes, including the one from my suggestion. I'll do a quick review to make sure everything is fine.

[darccio]

Thanks @knusbaum!

[cbeauchesne]

@darccio I'm a little bit worried to see a file impacting all parametric scenrio modified, and 5 parametric job failing on the last commit. Are you 100% sure it's not related?

[cbeauchesne]

So, my bad, you didn't merged it in main. I need some rest 😅