Add a new contribution rule: Restrict projects that are unused and are not unique from being submitted

[yassinebenaid]

A lot of PRs are submitting new projects. And, in a lot of cases, they are just redundant packages that do something one or more popular projects are doing it years before.

An example would be packages for task management (cron implementations), reflection packages, config files loaders, web frameworks, dependency injection and many more.

These are the top categories that receive the most of new projects. That is not a problem, until it is.

A lot of newly submitted packages are doing the exact same thing, may be some API differences but still have the same interface, the same functionality and for the same use case.

So my suggestion is to add a new contribution rules that indicate:

1. Not to submit new projects that don't have any or very few active users (we can specify a minimum threshold of stars for example)
2. We may break rule number 1 if, the project is offering a unique functionality that none or only few actively maintained projects are offering.
3. We may break rules number 1 and 2, if the project is considered better that others in some way (performance, adds new functionalities others are missing, ... etc)

Of course we can break all above rules in very rare cases depending on situation. However, PRs that break above rules will be closed.

Any thoughts @avelino @phanirithvij