Fix valgrind failure in STM

[zachmprince]

Reason

Closes #30141

Design

There was some faulty logic in the SobolReporter that was causing it to output second-order indices even when they didn't exist. After fixing this, I realized there really should be a proper unit test to do a non-resampled sobol computation, so I added that.

In preparation of a new testing paradigm for examples. I renamed the test spec for the workshop so it wouldn't be run by default. Instead it would be run in something like this recipe: https://civet.inl.gov/job/2758375/

Impact

Non-buggy code.

[moosebuild]

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

View the site here

This comment will be updated on new commits.

[loganharbour]

Optimization failure is unrelated. Waiting on examples in https://civet.inl.gov/job/2759912/

[moosebuild]

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

Framework coverage

	8960f3	#30142 a977d3
	Total	Total	+/-	New
Rate	85.28%	85.28%	+0.00%	-
Hits	109358	109359	+1	0
Misses	18883	18882	-1	0

Diff coverage report

Full coverage report

Modules coverage

Stochastic tools

	8960f3	#30142 a977d3
	Total	Total	+/-	New
Rate	90.64%	90.64%	-	100.00%
Hits	8104	8104	-	2
Misses	837	837	-	0

Diff coverage report

Full coverage report

Full coverage reports

Reports

• framework
• 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.