chore(ci): add goleak to TestMain
Whilst this isn't as helpful as a per test defer goleak.VerifyNone in terms of showing which test was responsible for the leak, it's still worth having as a baseline check in PRs and CI to prevent new leaks being introduced now that we're all cleaned up. If a PR fails we can subsequently run tests individually in order to determine which one is the leaker.
See https://github.com/uber-go/goleak#quick-start and https://github.com/uber-go/goleak#determine-source-of-package-leaks
Thank you for your contribution! However, this pull request has not had any activity in the past 90 days and will be closed in 30 days if no updates occur. If you believe the changes are still valid then please verify your branch has no conflicts with main and rebase if needed. If you are awaiting a (re-)review then please let us know.