fix: Disable CI/CD linter check with rand library, fix server overlap, and data race issue

[Manav-Aggarwal]

Resolves#911, resolves#919, resolves#910

[codecov]

Codecov Report

Patch coverage: 55.55% and project coverage change: -0.28⚠️

Comparison is base (ee5582f) 56.11% compared to head (4b6ef57) 55.84%.

Additional details and impacted files

@@ Coverage Diff @@## main #916 +/- ##
==========================================
- Coverage 56.11% 55.84% -0.28% 
==========================================
Files 66 66 Lines 10705 10709 +4 ==========================================
- Hits 6007 5980 -27 - Misses 3830 3858 +28 - Partials 868 871 +3 

Impacted Files	Coverage Δ
p2p/client.go	60.49% <ø> (+1.23%)	⬆️
p2p/gossip.go	75.92% <42.85%> (-6.08%)	⬇️
libs/testfactory/txs.go	72.22% <100.00%> (ø)

... and 4 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[smuu]

In my opinion, the PR title and later the commit message should not contain "Resolve" because this PR does not resolve the security warning, it just disables the check.
I'm okay with not fixing it because it's used in the tests. But this should not be used in production code.

[Manav-Aggarwal]

In my opinion, the PR title and later the commit message should not contain "Resolve" because this PR does not resolve the security warning, it just disables the check. I'm okay with not fixing it because it's used in the tests. But this should not be used in production code.

Since the math/rand library is used across multiple files, there's not just one place where we can put a warning. Where do we think is it most appropriate to document the math/rand warning if we don't want it to be used in production?

[smuu]

LGTM

Race test fail