strip ALL pact value infos, recursively as well, add tests

[jmcardon]

See #1284 for sample output

PR checklist:

• Test coverage for the proposed changes
• PR description contains example output from repl interaction or a snippet from unit test output
• Documentation has been updated if new natives or FV properties have been added. To generate new documentation, issue cabal run tests. If they pass locally, docs are generated.
• Any changes that could be relevant to users have been recorded in the changelog
• In case of changes to the Pact trace output (pact -t), make sure pact-lsp is in sync.

Additionally, please justify why you should or should not do the following:

• Confirm replay/back compat
• Benchmark regressions
• (For Kadena engineers) Run integration-tests against a Chainweb built with this version of Pact

[jmcardon]

Note: stripPactValueInfo above isn't even enough, the author of that code did not cover PGuard which can recursively contain pact values, the tests in this PR in hash.repl have a case with a user guard which does indeed fail if not stripped recursively.

[jmcardon]

this covers all cases recursively for my-mod.

PactValues are:

• lists
• objects
• guards (can contain them recursively too)
• literals
• modrefs

Literals cannot contain any pactvalues, so it's just the other 3 cases we must check.