The Performance Lab plugin has had a generator meta tag since shortly after its launch (see #321). Now that we are publishing the modules as standalone plugins and eventually will break them out, we need to also iterate on how that generator tag includes the relevant information. We would still want to make sure the generator tag includes which of the modules or equivalent standalone plugins the site uses.

I can see two alternative approaches for this:

1. Either we include the module name in the generator tag like we do today, even if it's actually the module's equivalent standalone plugin that is being used.
2. Or we keep the existing generator tag as is, only for modules, and introduce a second generator tag that captures any of the standalone plugins including their versions.

On the one hand, approach 1. is simpler and ties in seamlessly with how the generator tag works today. Any tooling that makes use of the data to measure adoption (using the public HTTP Archive dataset) will continue to function without modifications.

On the other hand, approach 2. would clearly separate which features are used as modules vs which features are used as plugins, and it could also include each standalone plugin's version number. This provides more information, but is also a bit more effort and might be unnecessarily verbose.

Do we actually need the additional information that approach 2. provides? If yes, I think we should go with it. If not, I think we should go with approach 1.