Local error golden test functions

[newhoggy]

Changelog

- description: |
    Import from `cardano-api` into local functions:
    * `testAllErrorMessages`
    * `testAllErrorMessages_`
    *  `testErrorMessage`
    Call `watchdogProp` when running golden error tests
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  - refactoring    # QoL changes
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context

Additional context for the PR goes here. If the PR fixes a particular issue please provide a link to the issue.

How to trust this PR

Highlight important bits of the PR that will make the review faster. If there are commands the reviewer can run to observe the new behavior, describe them.

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated. See Running tests for more details
• Self-reviewed the diff

[erikd]

Why is this needed? Would be nice to have a comment explaining why.

[newhoggy]

One of the Windows builds fails otherwise. The asn1-encoding package fails to build because it generates warnings on Windows and our build errors out on warnings.

[newhoggy]

Comment added.

[Jimbo4350]

Why are you moving the functions here?

[carbolymer]

I have the same question as @Jimbo4350 . Why vendor in functions here, rather than fixing them upstream?

I'm not convinced this PR is a net benefit because I haven't seen hangups in golden tests in cardano-api and we are using those functions there as well.

@newhoggy Have you seen hangups in error messages' goldens? Have you seen them in cardano-api as well?

[newhoggy]

The reason I want this is there are unexplained hangs and if watchdogProp can catch it I can log which test it is and there was one hang where this test was the last test that ran.

If watchdogProp doesn't wrap a test and I run a test and it hangs, I can't tell if it's one of the unwrapped tests.

The PR is not meant to be permanent. When the root cause of the hangs are determined, this can be rolled back and any changes upstreamed.

Replied