This adds a tool for extracting changelog from the CHANGELOG.md file to
ease up release notes creation.

binary uploads are failing because we moved this repo from the `uber`
GitHub org to `uber-go` GitHub org, so uploads are getting 307 response.

…#63)

Closes #58.

This is a proposal PR to generate mocks without error for following
cases:
```go
type Water[R any, C UnsignedInteger] interface {
	Fish(R) []C
}

type UnsignedInteger interface {
	~uint | ~uint32 | ~uint64
}
```

Go `types` package seems to wrap interfaces that contain type
constraints by checking a type set literal of the form `~T` and `A|B`.
https://github.com/golang/go/blob/master/src/go/types/decl.go#L668

So gomock can just ignore that pattern to generate mocks safely without
`don't know how to mock method of type` errors. I think this can be a
better solution for custom type constraints than [`-exclude`
flag](#72).

---------

Co-authored-by: Jacob Oaks <jacoboaks.8@gmail.com>

While Uber has forked mock the CONTRIBUTRORS file still reflects
Google's contents. Delete the file for now to prevent confusion.

Now that we've removed the old CONTRIBUTORS file, update the
CONTRIBUTING.md with a tip for signing Uber's CLA.

This follows the CONTRIBUTING.md tip for Fx.
ref: https://github.com/uber-go/fx/blob/master/CONTRIBUTING.md

…e comments (#112)

This allows package comments to be generated following the rules here:
https://staticcheck.io/docs/checks#ST1000

**Before:**
```go
//	mockgen -destination demo/mock.go -package demo . Demoer
//
// Package demo is a generated GoMock package.
package demo
```

**After:**
```go
//	mockgen -destination demo/mock.go -package demo . Demoer
//

// Package demo is a generated GoMock package.
package demo
```

Add a matcher for matching against regular expressions

To fix unit test on windows and address #120

fix misspell

To address #118

---------

Co-authored-by: Marten Seemann <martenseemann@gmail.com>

I forgot to do this when I created the last PR
#72

When you are trying to mock multiple interfaces with the same name and
similar methods (for example user.Service Create, post.Service Create,
etc..) there is collision in Recorder and ReturnCall types, the
-mockNames parameter only changes the main interface name, with the
changes proposed in this PR the correct mockName will be applied to the
Recorder and ReturnCall types.

Addresses #117

When a package name is "any" mockgen will use that as a package name in
the generated code which causes issues due to colliding with Go's "any"
type. Update the sanitization logic to prevent this collision.