Requested in #171 (comment)

Allow the generation of mocks for generics as introduced in golang 1.18

- Only test on 1.19 for Windows and Mac.
- Bump versions for checkout and setup-go actions. Use cache flag in
  setup-go instead of separate cache step.

By tweaking whitespace in template

When we generate a unique name for pkg a on conflict with pkg b, the new
name could already be in use for pkg c. So recursively check each unique
name against existing imports before setting it.

The optional with-resets flag adds methods to reset method calls. Calls
can be reset individually or all at once with these.

Signed-off-by: Gabriel Bussolo <[email protected]>
Co-authored-by: Mat Ryer <[email protected]>

- Add benchmark test for registry.New

Co-authored-by: ccoVeille <[email protected]>

* Fix GitHub check annotations

* Update types.go

- Bump golang ver => 1.22.5

Go 1.23 changed how go/types handles type aliases, which breaks code
generation if you use a package that has an alias type (example:
https://pkg.go.dev/github.com/golang/[email protected]/ptypes/timestamp#Timestamp
). These were getting generated as just the unqualified name, without
the package. If you used a previous version of Go, it meant that if that
aliased type was in an internal package we'd try to import the internal
package instead, resulting in a compilation error.

Add a switch to handle that case, and bump the go.mod version to support
using types.Alias.