Issues with long path names for feature edges

[wyldckat]

snappyHexMesh uses an interesting feature from OpenFOAM: it can lookup feature edge mesh files and triSurface files from both the current processor folder and the root folder of the case.

Now, this is nice and all, but on Windows it leads to the issue where the case folder might use one convention of folder name and the feature edge mesh folder/path uses another, e.g.:

C:/cases/long_case_name
//?/c/cases/long_case_name/processor0/constant/triSurface/geom.stl

This means that the method Foam::fileOperations::masterUncollatedFileOperation::filePath will not work properly on Windows.

The workaround is to use show path names for everything or perhaps enforce both paths to use UNC, but still...

[wyldckat]

Note: OpenFOAM 12 has changed things considerably, so it's not easy to test this out-of-the-box with an old case.

[wyldckat]

TODO Adopting the long path support in general, i.e. UNC variant of the path when the path is too long, e.g. asLongPath in the class fileName.

1. This is because both creating folders and filenames themselves will need special handling of the paths.
2. In the meantime, we can provide the -case argument with the UNC form of the current path, if need-be, in order for it to be inherited.

This comment is a follow up to what was done in the following commits:

• https://github.com/blueCFD/OpenFOAM-dev/commit/f7a6892a70b5c0b8d70ca2fdbe995868165b6c32
• https://github.com/blueCFD/OpenFOAM-dev/commit/d59d3853cd0e70cc45046d6fbe19c5e3a1badfc6
• https://github.com/blueCFD/OpenFOAM-dev/commit/49891e034ae36564a21e45237572d97ff8d2ba9a
• https://github.com/blueCFD/OpenFOAM-dev/commit/b4395ab9acb0228dd0ee2e290b5547a1a4c89799