Skipping racy tests

[3vilhamster]

What changed?
Skipping racy test to improve CI stability.

Why?
These tests are leaking go routines and cause failures of the tests both local and on CI.
This is due to leaking goroutine and a lack of control of workflow.Go spawned gorouotines.
I've created a ticket for a depper investigation, but skipping it for now.

How did you test it?

Potential risks

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.23%. Comparing base (847db44) to head (9e69ebd).
Report is 1 commits behind head on master.

Additional details and impacted files

see 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 847db44...9e69ebd. Read the comment docs.

[Groxx]

aaagh:

==================
WARNING: DATA RACE
Read at 0x00c00052e043 by goroutine 141:
  testing.(*common).logDepth()
      /opt/hostedtoolcache/go/1.22.8/x64/src/testing/testing.go:1017 +0xcd
  testing.(*common).log()
      /opt/hostedtoolcache/go/1.22.8/x64/src/testing/testing.go:1010 +0xa4
  testing.(*common).Logf()
      /opt/hostedtoolcache/go/1.22.8/x64/src/testing/testing.go:1061 +0x6a
  testing.(*T).Logf()
      <autogenerated>:1 +0x69
  go.uber.org/zap/zaptest.testingWriter.Write()
  ...

Previous write at 0x00c00052e043 by goroutine 138:
  testing.tRunner.func1()
      /opt/hostedtoolcache/go/1.22.8/x64/src/testing/testing.go:1676 +0x8fa
  runtime.deferreturn()
      /opt/hostedtoolcache/go/1.22.8/x64/src/runtime/panic.go:602 +0x5d
  testing.(*T).Run.gowrap1()
      /opt/hostedtoolcache/go/1.22.8/x64/src/testing/testing.go:1742 +0x44

that log-race is quite annoying.
I'll make a PR for it, and maybe we can pull my safe-logger-shim over from the server.