refactor(log/logtest): update AssertEqual to accept TestingT for benchmark support

[flc1125]

This might just be a minor optimization, a non-functional change. Perhaps it can skip the CHANGELOG.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.9%. Comparing base (2cce189) to head (77236b9).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #6908     +/-   ##
=======================================
+ Coverage   82.3%   82.9%   +0.6%     
=======================================
  Files        263     261      -2     
  Lines      24476   24259    -217     
=======================================
- Hits       20151   20122     -29     
+ Misses      3942    3760    -182     
+ Partials     383     377      -6     

Files with missing lines	Coverage Δ
log/logtest/assert.go	100.0% <100.0%> (ø)

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[dmathieu]

Skipping changelog, as this module isn't released yet.

[pellared]

I am not sure we are inn favor of this change.

Please see the conversation here: See: #6662 (comment)

My initial proposal was to expose TestingT interface to make it even easier to reuse as this would be a "thinner" interface (so that e.g. https://pkg.go.dev/github.com/goyek/goyek/v2#A would implement this interface).

// TestingT reports failure messages.
// *testing.T, *testing.B, *testing.F  implement this interface.
type TestingT interface {
	Errorf(format string, args ...any)
}

What are the benefits of using testing.TB over exposing our own interface?
How this change addresses concerns from the original proposal.

[flc1125]

TestingT

I also agree with exposing the TestingT interface. Apply the principle of least privilege. This way, control can be higher.