Add SymmetryTransformerGenerator, with plane symmetry only currently

[RocksSavage]

Beware, the option to optionally use StitchedMeshGenerator has not been tested. Tests have not been written.
I would appreciate it if the test currently in simple.i would end up in the documentation as an example of what
default parameters are ran when the stitch option is exercised.

• add tests
• add stitching capability
• document extent of support in md file

Refs #21578

[GiudGiud]

This is on hold until we can get better fixing of negative volumes in libmesh

[GiudGiud]

This will be near-ready on the next libmesh submodule update.

[GiudGiud]

@loganharbour this should be ready for review please

[GiudGiud]

nevermind still no libmesh update

[GiudGiud]

@loganharbour ready for review.

I've had to add a bit of lower quality code (const_cast) to allow for a sub-generator to run after a main generator.
If that's not agreeable, then I reckon I want to delete the stitching and get this merged.

[moosebuild]

Job Documentation on 917e4f8 wanted to post the following:

View the site here

This comment will be updated on new commits.

[moosebuild]

Job Coverage on 917e4f8 wanted to post the following:

Framework coverage

	e4507b	#21718 917e4f
	Total	Total	+/-	New
Rate	84.53%	84.54%	+0.01%	87.50%
Hits	81696	81735	+39	35
Misses	14946	14947	+1	5

Diff coverage report

Full coverage report

Modules coverage

Coverage did not change

Full coverage reports

Reports

• framework
• chemical_reactions
• combined
• contact
• electromagnetics
• external_petsc_solver
• fluid_properties
• fsi
• functional_expansion_tools
• geochemistry
• heat_conduction
• level_set
• misc
• navier_stokes
• optimization
• peridynamics
• phase_field
• porous_flow
• ray_tracing
• rdg
• reactor
• richards
• scalar_transport
• solid_properties
• stochastic_tools
• tensor_mechanics
• thermal_hydraulics
• xfem

Warnings

• framework new line coverage rate 87.50% is less than the suggested 90.0%

This comment will be updated on new commits.

[loganharbour]

I'm really against the subgenerator for a few reasons:

1. The implementation of the before action is poor. This is resolvable and thus is minor.
2. I think that it will be confusing if we allow the addition of subgens like this. We could end up in a position where we could end up with a wonky graph that isn't intuitive to debug.
3. The action of the stitching is so simple and only requires copying one input to another in another MG. I think it's a poor use of the subgenerator system. It makes it look like we're okay with having a ton of meta generators - which I think is a poor idea because the best part of the MG system is its pluggability, and having to maintain all of that meta interaction sounds awful.

[moosebuild]

All jobs on 48111e4 : invalidated by @GiudGiud

[GiudGiud]

Should be good now

[GiudGiud]

Thanks for the contribution @RocksSavage !
I hope all is well in Utah