Add bundling capability

[siefkenj]

Use nodejs and vite to bundle CSS for distribution.

[rbeezer]

• Looks like this needs more of "our" files? crc style? More color options?
• I'm reluctant to get in the business of maintaing current copies of "other" CSS/JS, e.g. Prism.js. For example, many projects will never have a program element, and in this case, we won't even try to get the relevant support from a CDN at all. Bundled, every project will have it, need it or not. Current practice is consistent with how we only load LaTeX packages that are necessary, baed on inspection of the source.

[siefkenj]

• Looks like this needs more of "our" files? crc style? More color options?

Absolutely. This PR was a proof of concept. I was hoping someone who knows more of the pretext configuration options would create folders for each configuration.

• I'm reluctant to get in the business of maintaing current copies of "other" CSS/JS, e.g. Prism.js. For example, many projects will never have a program element, and in this case, we won't even try to get the relevant support from a CDN at all. Bundled, every project will have it, need it or not. Current practice is consistent with how we only load LaTeX packages that are necessary, baed on inspection of the source.

This could certainly be a secondary priority, but I really don't like relying on CDNs for all of these dependencies. I had a project that used MathJax from 10 years ago. Last time I checked, it stopped working because MathJax stopped running their CDN. Textbooks should be viewable for 30+ years. I do not trust any CDN that currently exists to be around at the same URL in 30 years.

The multiple configurations issues should be easy to solve though. Since once the CSS is bundled (part of the bundling involves re-writing any CSS imports to read from ./ instead of whatever path they used before), the files can just be concatenated. This should be really easy for the CLI to do.