Updating CONTRIBUTING.md with new/relevant context

[bnb]

Given that we've got a few changes coming down the pipeline around membership, I figured now is a good time for us to give the Community Committee's CONTRIBUTING.md file a bit of polish. There are a few things that need to be updated and included.

Here's a list of some of the things that need to be changed in the file:

• Vocabulary needs to be updated with our new terminology
• Update Teams and Working Groups to reflect current state of our work. This includes adding initiatives and removing Working Groups language.
• Fix non-existant in Teams and Working Groups.
• Some of the language in Logging Issues is outdated, including usage of Community Committee Collaborators and mention of security disclosure (as far as I know we don't have anything that would fall under security disclosure!)
• Contributions can/should be updated with more recent context around how we approach contributions to the Community Committee. I'm not sure if we also want to add a section pointing people to the initiatives here 🤔
• Becoming a Member and Collaborator needs an overhaul, specifically the ones outlined in Draft language based on discussions for CommComm Restructuring Efforts  #294
• Mentions of membership in CommComm Process needs to be updated.

If you want to take on any of these, feel free to comment on your interest here or just start working on a PR! ❤️

[Tiriel]

I'm going to up this a bit. I'll try working on some things ASAP, but lots to be done 😅

[WaleedAshraf]

I'll try to pick some of these.
Ping @nodejs/community-committee members.

[bnb]

I can mentor non-CommComm members on this one if they'd like to try to contribute 👍

[amiller-gh]

Was going to take this when making my updates to the README – looks like I forgot :) Re-adding the labels, may get back to it in the next day or so, thanks for the reminder.

[07Gond]

Hi y'all!
Can I help with this? 😄

[keywordnew]

@07Gond Of course. I'd suggest forking this repo, making changes (listed in first comment), opening a draft PR, linking to this issue from the PR, and asking any questions that you may need answered to complete the PR. You may also choose what process works best for you!

[bnb]

Un-assigning @amiller-gh since I don't think we've seen traction on this. I may try to take a peek at addressing this in the next few weeks. Definitely still very needed.

[Trott]

I've unarchived this repo so I can close all PRs and issues before re-archiving.