Decide on a policy on Emulator inclusion criteria

Should we have 2 sets, mainstream + less curated one (include all the OSS/spontenous requests from auhtors)?

Or just accept any emulator on the main one?

CI pipelines load may be an issue if we start adding a lot of emulators

Review the current emulator list and the CI pipelines before deciding whether to maintain one set or separate mainstream and less-curated sets. Compare the expected emulator coverage with CI pipeline load, then document a settled inclusion policy and its effect on the sets.

Written by the indexing model from the issue text.