docs: update contributing guidelines for required org membership

[JamieDanielson]

Which problem is this PR solving?

It should be easier to auto-assign issues and PRs and grant more authority to codeowners on specific packages.
This came up while reviewing the react-native instrumentation, which is currently the top requested feature in the repo. We want to delegate responsibly, while still keeping a high bar for adding instrumentations.

Short description of the changes

Update contributing guidelines to

• require membership in the OpenTelemetry org
• add owners to js-contrib-triagers role (role request in community repo)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.75%. Comparing base (162feb1) to head (66749ed).
Report is 11 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2548   +/-   ##
=======================================
  Coverage   90.75%   90.75%           
=======================================
  Files         169      169           
  Lines        8018     8018           
  Branches     1632     1632           
=======================================
  Hits         7277     7277           
  Misses        741      741           

see 1 file with indirect coverage changes

[trentm]

Isn't https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/.github/workflows/component-owners.yml already meant to be handling assigning PRs to and/or request reviews from component owners?

From https://github.com/dyladan/component-owners#readme

Automatically add component owners as assignees and approvers to pull requests.

This works very similarly to CODEOWNERS, however with CODEOWNERS all owners must have write access to the repository. ...

[pichlermarc]

This works very similarly to CODEOWNERS, however with CODEOWNERS all owners must have write access to the repository. ...

Aah, yes I completely forgot about this 🤦 CODEOWNERS does not work with non-write permission owners. 😞

Anyway I think we can still do something similar with component-owners.yaml and since we will give owners triage permissions they can then apply a label that a PR is ready to merge. Then approvers/maintainers can just swoop in and merge the PR. 🙂

[JamieDanielson]

@trentm @pichlermarc I removed the references to CODEOWNERS and just kept in the triagers role and the requirement of being in otel org.