topoSet: allow use of 'zone' instead 'set', 'zones' instead of 'sets' in all set sources

Summary

Everywhere a topoSetSource uses a (file-based) set allow use of a (mesh-based) zone.

Resolved bugs (If applicable)

Details of new models (If applicable)

If the keyword 'zone' is found instead of 'set' it instead uses the name to lookup the corresponding zone from the mesh. The advantage of a mesh-based zone is that they get updated if the mesh is updated.

Risks

Change to user input: everywhere in a topoSetDict can use 'zone' or 'zones' instead of 'set' or 'sets'.

assigned to @mark

Probably merge after merging feature-topoSet (adds optional transformation of cellCentres etc.) to avoid conflicts on that one. Not a big issue though.

added 6 commits

• 662bd47c...3ef892b9 - 5 commits from branch develop
• 79bae4dc - ENH: topoSet: allow use of 'zone' instead 'set'

Compare with previous version

added 1 commit

• f27d3448 - ENH: topoSet: allow use of 'zone' instead 'set'

Compare with previous version

mentioned in commit 77ec7ab6

merged

compressible/overRhoPimpleDyMFoam/twoSimpleRotors modifying topoSetDict as:

    {
        name    c0;
        type    cellSet;
//        type    cellZoneSet;
        action  new;
        source  regionsToCell;
        insidePoints ((0.001 0.001 0.001));
    }

    {
        name    c1;
//        type    cellSet;
        type    cellZoneSet;
        action  new;
        source  cellToCell;
        set     c0;
//        zone    c0;
    }

Using cellZoneSet at both levels and only zone setup for second operation -> works OK

However, using cellSet on first operation and aiming to create cellZoneSet on the basis of cellSet leads to error

--> FOAM FATAL ERROR: (openfoam-2401 patch=240220)
Attempt to cast type cellSet to type cellZoneSet

Am I missing anything?

mentioned in issue #3126 (closed)