fix(Eventually): fixed go routine leak issues

Reference (original issue report): stretchr#1611

This fix involves a complete rewrite of assertions that run background
checks, with more idiomatic go routine codes and use of context.Context.

Affected assertions:

* Eventually
* Never
* EventuallyWithT

We no longer run go routines that are not waited for.
Timeouts and early exits are handled via context.Context.

CollecT.FailNow() now also cancels the context of the caller instead.

Significant changes:
* callers should not expect Eventually and others to
  complete in the case of a blocking condition function.
  In particular, the condition function should never wait for an event that is
  triggered after Eventually. Complex or long-running condition function
  may use t.Context() to exit early if the test is failed.
* callers may safely assume that only one go routine is executing the
  condition function (no race on writes)

* test: asserted stretch/testify#480 is fixed

Signed-off-by: Frederic BIDON <fredbi@yahoo.com>

Author: fredbi

internal/assertions/compare_test.go

@@ -5,7 +5,6 @@ package assertions
 
 import (
 	"bytes"
-	"fmt"
 	"iter"
 	"runtime"
 	"slices"
@@ -194,24 +193,6 @@ func TestCompareMsgAndArgsForwarding(t *testing.T) {
 	}
 }
 
-type outputT struct {
-	buf     *bytes.Buffer
-	helpers map[string]struct{}
-}
-
-// Implements T.
-func (t *outputT) Errorf(format string, args ...any) {
-	s := fmt.Sprintf(format, args...)
-	t.buf.WriteString(s)
-}
-
-func (t *outputT) Helper() {
-	if t.helpers == nil {
-		t.helpers = make(map[string]struct{})
-	}
-	t.helpers[callerName(1)] = struct{}{}
-}
-
 // callerName gives the function name (qualified with a package path)
 // for the caller after skip frames (where 0 means the current function).
 func callerName(skip int) string {