Branch protection rule audit

[trask]

First pass:

• opentelemetry.io
  • missing **/** branch protection rule
• opentelemetry-dotnet
  • missing main branch protection rule
  • missing **/** branch protection rule
• opentelemetry-python
  • missing **/** branch protection rule
• opentelemetry-erlang
  • missing **/** branch protection rule
• opentelemetry-cpp
  • missing **/** branch protection rule
• opentelemetry-php
  • missing **/** branch protection rule
• opentelemetry-python-contrib
  • missing **/** branch protection rule
• opentelemetry-swift
  • missing **/** branch protection rule
• opentelemetry-go-contrib
  • missing **/** branch protection rule
• opentelemetry-dotnet-contrib
  • missing main branch protection rule
  • missing **/** branch protection rule
• opentelemetry-dotnet-instrumentation
  • missing **/** branch protection rule
• opentelemetry-lambda
  • missing **/** branch protection rule
• opentelemetry-erlang-contrib
  • missing **/** branch protection rule
• opentelemetry-network
  • missing main branch protection rule
• opentelemetry-collector-releases
  • missing **/** branch protection rule
• opentelemetry-demo
  • missing **/** branch protection rule
• opentelemetry-sandbox-web-js
  • missing main branch protection rule
• opentelemetry-php-instrumentation
  • missing main branch protection rule
• stackoverflow2slack
  • missing main branch protection rule
• opentelemetry-ebpf-profiler
  • missing main branch protection rule
  • missing **/** branch protection rule
• sig-mainframe
  • missing main branch protection rule
• sig-developer-experience
  • missing main branch protection rule
• gh-manager
  • missing main branch protection rule
• changelog.opentelemetry.io
  • missing **/** branch protection rule

[trask]

Thinking about this a bit... I'd like to propose removing the **/** branch protection rule, and instead:

• add an open-telemetry org rule set that enforces EasyCLA on main
• add an automation to check that all "long-term" repo branches other than main have EasyCLA enforced via either a branch protection rule or a rule set
  • probably will need to look over all repo branches to see what patterns people are using for "long-term" branch names

This will help us start moving towards rule sets and simplify some of the repo set up and auditing.

Note: I'm officially giving up on Rulesets until https://github.com/orgs/community/discussions/61107#discussioncomment-6569780 is fixed 😞

[trask]

Related: open-telemetry/community#2737

[trask]

Putting this work on hold until we get resolution on open-telemetry/community#2744