Handle long module path names on Windows

[tbirdso]

See cxx failures due to long module name: https://github.com/KitwareMedical/ITKMorphologicalContourInterpolation/actions/runs/3622628311/jobs/6107569800

[dzenanz]

I assume we should be able to apply this trick?
https://github.com/KitwareMedical/ITKUltrasound/blob/ca4e8bcb3183f591b29fbe9cf569bc08b3f0eba4/.github/workflows/build-test-package.yml#L322-L326

[tbirdso]

Yes, but as changing the module name obscures the directory structure and makes debugging more difficult it would be highly preferable to only change the working directory where needed, i.e. on Windows. Working to determine whether this can be done by setting environment variables to persist across Github Actions steps.

[thewtex]

Worth investigating going up another directory here:

ITKRemoteModuleBuildTestPackageAction/.github/workflows/build-test-cxx.yml

Lines 94 to 96 in 31f0dd5

	file(TO_CMAKE_PATH "\$ENV{GITHUB_WORKSPACE}/.." CTEST_DASHBOARD_ROOT)
	file(TO_CMAKE_PATH "\$ENV{GITHUB_WORKSPACE}/" CTEST_SOURCE_DIRECTORY)
	file(TO_CMAKE_PATH "\$ENV{GITHUB_WORKSPACE}/../build" CTEST_BINARY_DIRECTORY)

i.e.

         file(TO_CMAKE_PATH "\$ENV{GITHUB_WORKSPACE}/../.." CTEST_DASHBOARD_ROOT) 
         file(TO_CMAKE_PATH "\$ENV{GITHUB_WORKSPACE}/" CTEST_SOURCE_DIRECTORY) 
         file(TO_CMAKE_PATH "\$ENV{GITHUB_WORKSPACE}/../../build" CTEST_BINARY_DIRECTORY) 

[tbirdso]

After fiddling for too long today with passing environment path names between shells (bash, command prompt, powershell) I've decided preserving non-offending module directory names is not worth more time for investigation in the short term. Preparing a PR to simply move the working source directory to ../../im as we do in the Python workflow. If there is tangible negative impact on collaborators' investigation due to path renaming then I can spend more time on this in the future.