Migrate project-status repo back here

[tobie]

We should migrate https://github.com/openjs-foundation/project-status back to this repo and clean it up.

Would make maintenance of a number of cross repo documents easier.

Would make it easier for us to keep up to date with the status of the different projects.

[tobie]

Notes from today's CPC call:

• it would be great to have an issue board to better keep track of things
• might be nice to clean-up repo before moving it
• moving shouldn’t be too much work
• lukewarm consensus to migrate repos

[tobie]

Notes from this week's CPC call:

Working session on this next week

[tobie]

Notes from this week's working session call:

• Identify maintainers (and champions where appropriate) for each project
• if there are open questions, answer the question and tag them
• else, tag maintainers in a message asking them to update the checklist to reflect the current state of things

[tobie]

Started a project board to get us organized here: https://github.com/orgs/openjs-foundation/projects/9 (and asked @bensternthal to make it public).

[tobie]

Separately from the catching up work that's needed here, I still believe we should merge both repositories. Here's the rationale:

1. We're duplicating content across repos and keeping that content in sync is a drag (notably the checklists in PROJECT_PROGRESSION.md are copied in the issue templates).
2. Some CPC issues end-up in this repository (e.g. Should GOVERNANCE.md be required of all projects? project-status#47) and then get promptly forgotten.
3. Content in the project status repo (like the GROWTH plans) gets forgotten from CPC repo refactoring.

[bensternthal]

@tobie the board is already public :) Let me know if you need anything additional.