Freeze callstack in integration and integrationRetryWorkspace functions

[newhoggy]

Description

This is needed so that the generated module file contains the correct module name.

Before:

$ cabal test cardano-testnet --enable-tests --test-options '-p query-slot-number'
$ cat /private/tmp/nix-shell.wBf3gI/query-slot-number-0-test-744fa3ec7ae64cea/module
Testnet.Util.Base

After:

$ cabal test cardano-testnet --enable-tests --test-options '-p query-slot-number'
$ cat /private/tmp/nix-shell.wBf3gI/query-slot-number-0-test-744fa3ec7ae64cea/module
Test.Cli.QuerySlotNumber

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated. These may include:
  • golden tests
  • property tests
  • roundtrip tests
  • integration tests
    See Runnings tests for more details
• Any changes are noted in the CHANGELOG.md for affected package
• The version bounds in .cabal files are updated
• CI passes. See note on CI. The following CI checks are required:
  • Code is linted with hlint. See .github/workflows/check-hlint.yml to get the hlint version
  • Code is formatted with stylish-haskell. See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
  • Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7
• Self-reviewed the diff

Note on CI

If your PR is from a fork, the necessary CI jobs won't trigger automatically for security reasons.
You will need to get someone with write privileges. Please contact IOG node developers to do this
for you.

[newhoggy]

The workspace function reports the caller's module in the workspaces module file so that it is easy to find the failing test that created the workspace.

However, these functions are utility functions and we don't want to report Testnet.Util.Base. We instead want to report the module of the functions that call these functions. Hence we freeze the call stack.