docs: add table to prioritize scorecard implementation

[inigomarquinez]

Description

Based on an Excel sheet of @UlisesGascon with all the packages of the express ecosystem (updated 1st February 2024), I have divided them into 5 blocks of 10 repositories each (plus a block of repositories with low priority as they may be deprecated and another block of repositories that may not be the focus of the scorecard, as they are used for documentation) to prioritize the OpenSSF score card implementation.

For that, I have sorted the repositories by the number of downloads per week and assigned them a priority between 1 (the most important) and 5 (the least important) in the Scorecard priority block column. All those repositories with low priority have a priority of 6.

The table is then sorted alphabetically.

This is an initial version, so feel free to add your feedback.

Context

As part of the OpenSSF Scorecard implementation, the first step will be defining the scope and priority of each repo so we can divide efforts when adding the scorecard to each repo.

[UlisesGascon]

LGTM! Thanks for consolidate it @inigomarquinez 🙌

[wesleytodd]

Did we cross reference this with the this? expressjs/Admin#1

[carpasse]

@inigomarquinez I've done the cross reference against the repos listed in expressjs/Admin#1
Here are my findings:
packages-in-scope.md

Possible improvements to the scope table

1. Create a table per org.
2. Add a project name column
3. Sort table rows by project name. It makes everything easier to find

P.S. @wesleytodd I think some of the repos listed this PR are not listed in expressjs/Admin#1 I've listed them in the file with my findings in case you want to take a look

[inigomarquinez]

@carpasse , thanks for the idea. I've refactored the file to include the information you provide in the file in this commit

@wesleytodd , this should solve your comment.

[UlisesGascon]

LGTM! Thanks @inigomarquinez