Define how to implement Ecosystem for Project Browser

First step here would be to scrape the Drupal.org API and see if we can identify all the modules which have ecosystems set and what they are to come up with that unique list. Then we can brainstorm additional core components that we might want to include in a list.

We may want to get buy-in from Drumm and other webmasters that switching ecosystem to a taxonomy instead of the current method is an acceptable way to go and/or the right thing. They may prefer to have the entity-reference also include "core components" which might also solve the problem.

I think switching ecosystem to entity reference including core components could also be acceptable. That alone would not solve a major usability problem. When a project selects the ecosystem, the entire list of module projects is available (at least the last time I looked). It's a LONG list. There needs to be filtering on the selection, perhaps only those projects already selected as an ecosystem by another project? Or some way to allow a project to "opt-in" to be extended by other projects?

@chrisfromredfin Can you assign someone to scrape the Drupal API to see if we can get that initial list you suggested in #2? I don't think I have access and wouldn't know how to do that. (glad to learn, but...).

Edited the Issue Summary