Split resource assemblies into their own VSIXs automatically

[tmeschter]

Several repos, including dotnet/roslyn, ship their resource assemblies by just including them in the main VSIX they insert into the VS build. This works and is reasonably simple but means customers get resource assemblies for languages they don't care about. This incurs some time and disk space cost when downloading and installing the extra assemblies.

It would be very helpful if Arcade could automatically move the localized resources out of the main VSIX and into a set of per-locale VSIXs, with the main VSIX having an optional dependency on those. This way users only get the resource assemblies corresponding to their selected lang packs.

[tmeschter]

@tmat FYI.

[markwilkie]

@tmeschter - Do you know offhand who else this might help?

[tmeschter]

@markwilkie This could be of use to any component that ships binaries in VS. The ones I can think of right now are:

• dotnet/roslyn
• dotnet/project-system
• Microsoft/VisualFSharp
• dotnet/interactive-window

[tmat]

Probably msbuild as well. Essentially everyone who builds localized VSIXes for VS.

[markwilkie]

Makes sense. Moving to post //build (yell if that's not ok)