Moose Syntax Highlighting

[zachmprince]

Reason

Closes #30112

Design

The modification of the prism.min.js is the implementation of the syntax highlighting. The line for the moose input part was generated from my prism fork. Since I wanted to look more like the VSCode style, I modified the moose.css to include colors seen in the vscode theme that many of us use. Here is a snippet of what the highlighting looks like:

I went a little above-and-beyond, so to speak, and added links and tooltips to page documentation recognized by the syntax. For instance, clicking on [Functions] will take you to the Functions syntax page and ParsedFunction will take you to ParsedFunction.md. Also, hovering over the parameters and the class name (ParsedMaterial) will show the parameter/class description.

This is my first time writing JavaScript, so please go easy on my ignorance on how to code in that. All the python code and custom JS file is to support the syntax linking and description display. If we don't end up liking that, this is a much simpler PR.

Impact

The runtime for the doc build seems about the same. Pages with moose input listings do show some confusing text on the initial load, but quickly turn into the right thing once the JS is done. I don't see much other down sides other than we are dependent on a fork prism to get the syntax highlighting regex, but that is well documented in the prism.min.js file.

[loganharbour]

Not up to date with current packages

[moosebuild]

Job Documentation, step Docs: sync website on acec52e wanted to post the following:

View the site here

This comment will be updated on new commits.

[moosebuild]

Job Coverage, step Generate coverage on acec52e wanted to post the following:

Framework coverage

Mutiple base shas were found when retrieving head reports:
09b3c83
64da7a2

Modules coverage

Coverage did not change

Full coverage reports

Reports

• framework (FAILED)
• chemical_reactions
• combined
• contact
• electromagnetics
• external_petsc_solver
• fluid_properties
• fsi
• functional_expansion_tools
• geochemistry
• heat_transfer
• level_set
• misc
• navier_stokes
• optimization
• peridynamics
• phase_field
• porous_flow
• ray_tracing
• rdg
• reactor
• richards
• scalar_transport
• solid_mechanics
• solid_properties
• stochastic_tools
• subchannel
• thermal_hydraulics
• xfem

This comment will be updated on new commits.

[moosebuild]

Job Documentation on b94007b : invalidated by @zachmprince

Fetch error that's been resolved

[loganharbour]

All minor. Will require another re-do of the package bump

[moosebuild]

Job Precheck, step Versioner verify on acec52e wanted to post the following:

Versioner templates

Found 16 templates, 0 failed

Versioner versions

Found 10 packages, 2 changed, 0 failed

package	status	hash	to hash	version	to version
wasp	CHANGE	a8340b3	45a5f8b	2025.02.25 build 1	2025.03.26 build 0
moose-dev	CHANGE	00b281f	c355a34	2025.03.24	2025.03.26

[loganharbour]

Coordinate before merging because this is a package update.

[moosebuild]

Job Coverage, step Verify coverage on acec52e wanted to post the following:

The following coverage requirement(s) failed:

• Failed to generate framework coverage rate (required: 81.0%)