Fix MSA viz, new dependency specification options.

[dannon]

Primary driver was fixing the deployed MSA application on main -- this has been deployed to main in the usegalaxy branch as of last week and is working well to resolve our issues w/ msa. Specifying node package dependencies and relying on prebuilt visualization plugins (as implemented here) is going to make a huge difference in reliability moving forward.

In short, visualizations should prebuild and publish a static directory with whatever they need to run.

In package.json, that's this new part:

    "files": [
        "static"
    ],

Then the viz is published to npm like so: https://www.npmjs.com/@galaxyproject/msa

And then in the viz xml, we specify a particular version (or range, as appropriate) of plugin the viz is compatible with, like so:

    <requirements>
        <requirement type="package" version="0.2.1" package="@galaxyproject/msa"/>
    </requirements>

These requirements will all get staged to the Galaxy server's static file serving without a build process required, avoiding all of the issues we've had with differing node versions on novel and/or archaic systems.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[mvdbeek]

Are there any docs that would need updating ?

[dannon]

@mvdbeek Yes, and I'll add that to the list -- we'll want to update GTN tutorials, etc., though we may want to shift those to using a template Sam has been working on as a base visualization.

[github-actions]

This PR was merged without a "kind/" label, please correct.