Cohesive zone with mortar enforcement

[recuero]

Reason

There exists a CZM capability already in MOOSE which uses interface objects and material properties (see #11546, #18611, #18697).

We would like to have a cohesive zone modeling (CZM) capability that uses mortar based constraints, particularly that may leverage weighted nodal quantities. We posit that integrating the CZM formulations within a mortar constraint enforcement with mechanical contact will lead to better numerical convergence and possibly more accurate results.

Design

I initially plan on using the mortar user object design. If many lines of code are added, we will need to refactor the new classes.

Impact

Hopefully robustness and better physical modeling of the debonding process.

[lindsayad]

Would be great to remove the CZM interface-kernel based implementation altogether...

[recuero]

I second that. I believe we have everything we need to start working on this --the stateful property capability for mortar was a must. I am thinking that regular material properties would to some extent be replaced with node->property maps within the user object. That works just fine, but maybe we can think of a nicer, cleaner way of holding on to that data.

[lindsayad]

Then we could remove the BreakMeshByBlockGenerator ... my least favorite MOOSE object haha

[jiangwen84]

Having a Mortar-based CZM working in MOOSE provides a lot of benefits. However, for some cases, the interface-based CZM is conceptually simpler and more efficient, for example the grain boundary sliding in a polycrystalline material, and the DG-type fracture (CZM interface at all element edges). We need to think about how to make Mortar to efficiently handle a large number of contact pairs, and how to treat the triple/multiple junctions.

[recuero]

This is issue can be closed with #26309. Improvements on it can have their own issue.