Release 0.5.0

[Kielek]

Make 0.5.0-beta.1.

While creating PR

• update instrument.sh script to correctly set env. variables - https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/instrument.sh#L96-L98 - change netcoreapp3.1 to net.
• update OpenTelemetry.DotNet.Auto.psm1 -

  opentelemetry-dotnet-instrumentation/OpenTelemetry.DotNet.Auto.psm1

  Line 77 in 482e684

  $DOTNET_STARTUP_HOOKS = Join-Path $InstallDir "netcoreapp3.1/OpenTelemetry.AutoInstrumentation.StartupHook.dll"

  - change netcoreapp3.1 to net.

[pellared]

@open-telemetry/dotnet-instrumentation-approvers how about publishing this WITHOUT the beta.1 suffix and marking it a regular release (not a pre-release)? I think that 0.5.0 could be used in production. Moreover, take notice the auto-instrumentation is already used in OTel Operator and it also planned to be used in OTel Demo.

The main "problem" is that it is not stable and we can introduce breaking changes in next releases. Other OTel components are doing releases on non-stable releases (e.g. OTel Collector, OTel Operator).

What is more, OTel SDK 1.4.0 is still RC and we could create next release as 0.5.1-beta.1.

This proposal is (IMO) NOT violating https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/docs/versioning.md

[pellared]

SIG meeting: nobody objects in releasing as 0.5.0

[pellared]

https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/tag/v0.5.0