[golang] new orchestrion go weblog

[eliottness]

Motivation

Provide simple testing features for https://github.com/DataDog/orchestrion

Changes

• Copy-paste of the net-http variant into a net-http-orchestrion variant
• Removal of all dd-trace-go SDK usage in this new variant
• Creating a new install_orchestrion.sh script in the go weblog
• Adding utility features for orchestrion for feature parity with the tracer
• Changed 1 testsuite that had behaviour hardcoded for variant names
• Disable all the same tests that could not pass because of net-http lack of path params

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

• If PR title starts with [<language>], double-check that only <language> is impacted by the change
• 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
• A scenario is added (or removed)?
  • Get a review from R&P team

[cbeauchesne]

Globally, LGTM, i'v just two questions before approving