[repo] Release automation improvements

[CodeBlanch]

Relates to open-telemetry/opentelemetry-dotnet#5657

Changes

• Sets up the release automation to use OpenTelemetryBot
• Refactors post-release PackageValidationBaselineVersion PR update job from package workflow into a new workflow triggered by the release publish

Details

This PR syncs up contrib with the main repo such that the release automation uses OpenTelemetryBot.

Test runs:

• [repo] Prepare release Exporter.OneCollector-1.9.0-alpha.1 CodeBlanchOrg/opentelemetry-dotnet-contrib#8
• [repo] Prepare release Exporter.OneCollector-1.9.0 CodeBlanchOrg/opentelemetry-dotnet-contrib#9

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.09%. Comparing base (71655ce) to head (4a52e09).
Report is 291 commits behind head on main.

❗ Current head 4a52e09 differs from pull request most recent head a4949a7

Please upload reports for the commit a4949a7 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1866      +/-   ##
==========================================
- Coverage   73.91%   70.09%   -3.82%     
==========================================
  Files         267      296      +29     
  Lines        9615    10849    +1234     
==========================================
+ Hits         7107     7605     +498     
- Misses       2508     3244     +736     

Flag	Coverage Δ
unittests-Exporter.Geneva	52.08% <ø> (?)
unittests-Exporter.InfluxDB	95.88% <ø> (?)
unittests-Exporter.Instana	68.22% <ø> (?)
unittests-Exporter.OneCollector	89.46% <ø> (?)
unittests-Exporter.Stackdriver	75.73% <ø> (?)
unittests-Extensions	79.83% <ø> (?)
unittests-Extensions.AWS	83.41% <ø> (?)
unittests-Extensions.Enrichment	100.00% <ø> (?)
unittests-Instrumentation.AWS	80.30% <ø> (?)
unittests-Instrumentation.AWSLambda	87.96% <ø> (?)
unittests-Instrumentation.AspNet	74.55% <ø> (?)
unittests-Instrumentation.AspNetCore	85.27% <ø> (?)
unittests-Instrumentation.ElasticsearchClient	79.87% <ø> (?)
unittests-Instrumentation.EntityFrameworkCore	55.49% <ø> (?)
unittests-Instrumentation.EventCounters	76.36% <ø> (?)
unittests-Instrumentation.GrpcNetClient	79.61% <ø> (?)
unittests-Instrumentation.Hangfire	93.58% <ø> (?)
unittests-Instrumentation.Http	81.08% <ø> (?)
unittests-Instrumentation.Owin	83.43% <ø> (?)
unittests-Instrumentation.Process	100.00% <ø> (?)
unittests-Instrumentation.Quartz	78.94% <ø> (?)
unittests-Instrumentation.Runtime	100.00% <ø> (?)
unittests-Instrumentation.SqlClient	91.89% <ø> (?)
unittests-Instrumentation.StackExchangeRedis	71.00% <ø> (?)
unittests-Instrumentation.Wcf	48.91% <ø> (?)
unittests-PersistentStorage	65.44% <ø> (?)
unittests-Resources.AWS	75.27% <ø> (?)
unittests-Resources.Azure	78.35% <ø> (?)
unittests-Resources.Container	72.41% <ø> (?)
unittests-Resources.Gcp	72.54% <ø> (?)
unittests-Resources.Host	51.16% <ø> (?)
unittests-Resources.Process	81.81% <ø> (?)
unittests-Resources.ProcessRuntime	72.91% <ø> (?)
unittests-Sampler.AWS	87.97% <ø> (?)

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

see 311 files with indirect coverage changes

[Kielek]

LGTM

[Kielek]

Question related to the release-PRs:
Should PRs be tagged by the infra label? I think that it will be better to put there label related to the releasing artifacts. There is even a logic for tagging issues: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/4ee07f40efc5438816b718549fc99b6a0cdc3e1b/build/scripts/add-labels.ps1

[CodeBlanch]

Question related to the release-PRs: Should PRs be tagged by the infra label? I think that it will be better to put there label related to the releasing artifacts. There is even a logic for tagging issues: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/4ee07f40efc5438816b718549fc99b6a0cdc3e1b/build/scripts/add-labels.ps1

@Kielek I like it! I'll do as a follow-up.