Allow uikit plugins to be used across multiple uikit definitions

[Hydraner]

In patternlab-config.json it is possible to define multiple uikits with different configurations. As far as I understand, the idea is to have a workshop and a storefront uikit showing diffrent patterns based on the exclude configuration.
Since there is no dedicated storefront uikit at the moment, it would be nice if you could just use iukit-workshop to generate the patternlab frontend.

Expected Behavior

When I define multiple uikits with the same name, only one frontend is generated properly

Actual Behavior

Only the last one will work, since the config will override itself.

Steps to Reproduce

Put the following configuration into your patternlab-config.json
"uikits": [ { "name": "uikit-workshop", "outputDir": "workshop", "enabled": true, "excludedPatternStates": [], "excludedTags": [] }, { "name": "uikit-workshop", "outputDir": "storefront", "enabled": true, "excludedPatternStates": [ "inprogress" ], "excludedTags": [] }]

Proposed solution

In order to be backwards-compatible, I suggest adding an optional key "id" to the uikit settings, which will be used to collect the configuration instead of the name. If the id does not exists, use the name as fallback.

[mfranzke]

A mitigation in between might be to use package aliases:
npm i @pattern-lab/uikit-other@npm:@pattern-lab/uikit-workshop

This would install the @pattern-lab/uikit-workshop as an additional @pattern-lab/uikit-other.

Again, it's not a permanent solution, as it would increase the packages by another installation of the @pattern-lab/uikit-workshop files, but could solve your problems regarding this topic until the code of this issue gets merged.

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

[ringods]

Covered by #1225 (which was reverted and redone in #1246). The name remained the name, but the package property was added. You can use the same package but with different names.