Add no-merge capability to mesh combiner generator

[GiudGiud]

closes #27646

This could be stuff we push upstream to libmesh tbh. It's mostly there for blocks already.

[moosebuild]

Job Documentation on e224d50 wanted to post the following:

View the site here

This comment will be updated on new commits.

[dschwen]

So now it does the same thing MeshCollectionGenerator does?

params.addClassDescription("Collects multiple meshes into a single (unconnected) mesh.");

[moosebuild]

Job Coverage on e224d50 wanted to post the following:

Framework coverage

	4409da	#27647 e224d5
	Total	Total	+/-	New
Rate	85.15%	85.14%	-0.01%	75.71%
Hits	103914	103955	+41	53
Misses	18123	18139	+16	17

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_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
• thermal_hydraulics
• xfem

Warnings

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

This comment will be updated on new commits.

[GiudGiud]

The combiner has never been stitching. So imo the two objects have always been duplicating features, one with the added capability for positions (combiner) and the other one with the added check on sideset names/ids (collection).
The check on sideset names/ids would have been great on the combiner too

Except now there is code to prevent a merge which the MeshCollectionGenerator does not have. The mesh collection generator will still merge sidesets/blocks with the same ids if they are either unnamed or with the same name.

[GiudGiud]

Thanks for the review!
This will help interns with mesh generation I m fairly confident