Fix cache key collisions for paths with separators

[zanieb]

Closes #12158

Hashing Path does not take into account path separators so foo/bar is the same as foobar which is no good for our case. I'm guessing this is an upstream bug, perhaps introduced by rust-lang/rust@45082b0? I'm investigating that further.

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

ℹ️ ecosystem check encountered linter errors. (no lint changes; 1 project error)

demisto/content (error)

ruff check --no-cache --exit-zero --ignore RUF9 --output-format concise --preview

warning: The top-level linter settings are deprecated in favour of their counterparts in the `lint` section. Please update the following options in `pyproject.toml`:
  - 'ignore' -> 'lint.ignore'
  - 'select' -> 'lint.select'
  - 'unfixable' -> 'lint.unfixable'
  - 'per-file-ignores' -> 'lint.per-file-ignores'
warning: `PGH001` has been remapped to `S307`.
warning: `PGH002` has been remapped to `G010`.
warning: `PLR1701` has been remapped to `SIM101`.
ruff failed
  Cause: Selection of deprecated rule `E999` is not allowed when preview is enabled.

[zanieb]

Filed a bug report at rust-lang/rust#127254

[zanieb]

I think this fix is safe because it's what was done upstream until this regression was introduced rust-lang/rust@a083dd6

[MichaReiser]

Thank you!

We could also consider to hash the as_os_str because all we really care about is if the path changed and invalidating if the path changed but, technically is still equal, isn't a real concern.