chore: Replace reflect.DeepEqual with cmp.Equal in tests

[jferrl]

This PR refactors the test suite to replace all instances of reflect.DeepEqual with cmp.Equal from the github.com/google/go-cmp/cmp package. This change improves test performance, provides better error messages, and follows modern Go testing best practices. Also improves test output readability and consistency across the codebase

[gmlewis]

@jferri - just FYI - I lost write access to this repo and this may cause unexpected delays for which I apologize.
You can watch that other PR to check on the status.

[jferrl]

@jferri - just FYI - I lost write access to this repo and this may cause unexpected delays for which I apologize. You can watch that other PR to check on the status.

No worries! 😃

[alexandear]

I propose configuring the forbidigo linter in the golangci-lint config to forbid the use of reflect.DeepEqual in tests. This way, the use of cmp.Equal will be automatically enforced in the future.

[jferrl]

I propose configuring the forbidigo linter in the golangci-lint config to forbid the use of reflect.DeepEqual in tests. This way, the use of cmp.Equal will be automatically enforced in the future.

Thanks for the suggestion, good catch 😃

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.12%. Comparing base (3646f33) to head (a7aaaea).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3691   +/-   ##
=======================================
  Coverage   91.12%   91.12%           
=======================================
  Files         187      187           
  Lines       16640    16640           
=======================================
  Hits        15164    15164           
  Misses       1291     1291           
  Partials      185      185           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[gmlewis]

Thank you, @jferrl and @alexandear!
LGTM.
Merging.