Add coverage for uncovered user routes and suppress test request logs

[raymondjacobson]

Summary

• add route tests for /v1/users/top, /v1/users/:userId/subscribers, and /v1/users/:userId/muted using local in-file fixtures and jsonAssert
• avoid global fixture dependencies in the new tests by seeding only required rows per test
• disable Fiber request logging middleware in test env so passing test runs stay quiet and failures are easier to spot

Validation

• go test ./api -run "TestUsersTop|TestUsersSubscribers|TestUsersMuted" -count=1
• go test ./api -run "Test200UnAuthed" -count=1

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
28321821	Triggered	Generic High Entropy Secret	b04e3cc	api/v1_engagement_mutations_test.go	View secret
28321821	Triggered	Generic High Entropy Secret	b04e3cc	api/v1_engagement_mutations_test.go	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}