python venv cache support

[h0tw1r3]

hashFiles currently doesn't support globs outside of the GITHUB_WORKSPACE. This works around the limitation.

[2bndy5]

Just to be clear, this may not cache the clang-format nor clang-tidy executables.

Important

This might actually cache the executables on MacOS or Windows because our cpp-linter/clang-tools-pip tool will fall back to installing clang tools (static) binaries to the same directory that the python executable is located.
In the case of a venv, that default install location is /.env/Scripts/ on Windows or /.env/bin/ on MacOS (~/.local/bin/ on linux).

[2bndy5]

FYI, I think the CI failed on MacOS runners because of segfaults. This isn't anything to do with the changes here, rather we should look into this separately.

resolved

[2bndy5]

I also think there should be some logic added to detect presence of a cached venv before creating a venv.

cpp-linter-action/action.yml

Line 241 in a3ed755

${{ steps.setup-python.outputs.python-path }} -m venv "$GITHUB_ACTION_PATH/venv"

cpp-linter-action/action.yml

Line 277 in a3ed755

${{ steps.setup-python.outputs.python-path }} -m venv "$env:GITHUB_ACTION_PATH/venv"

The above lines might fail if the venv folder already exists.

[2bndy5]

I guess we should also cache pip's global cache as well if this new option is enabled.