moq should not follow type aliases to internal packages

[davidmdm]

Moq resolves type aliases which can lead to non-compilable code.

For example:

package main

import (
	"context"

	"cloud.google.com/go/pubsub"
)

//go:generate moq -out ./receiver_mock.go . Receiver
type Receiver interface {
	Receive(ctx context.Context, f func(context.Context, *pubsub.Message)) error
}

In the google pubsub package Message is declared as:

import (
  ipubsub "cloud.google.com/go/internal/pubsub"
)

...

type Message = ipubsub.Message

And this the code generated by moq resolves the type alias and produces:

package main

import (
	"cloud.google.com/go/internal/pubsub" // ERROR CANNOT COMPILE BECAUSE OF INTERNAL IMPORT
	"context"
	"sync"
)

// Ensure, that ReceiverMock does implement Receiver.
// If this is not the case, regenerate this file with moq.
var _ Receiver = &ReceiverMock{}

...

Ideally moq would generate the code using the non-internal import inferred from the type alias.