mock: allow testing for functional options

[nbaztec]

Summary

This PR fixes #997

In most go libraries nowadays (etcd, kubernets, aws, etc.) the functional options pattern is being used:

c := client.New(client.WithTimeout(), client.WithLabel("bar"))

type opt struct {
  timeout bool
  label string
}

type ClientOption func(*opt)

func WithTimeout() ClientOption {
  return func(o *opt) {
    o.timeout = true
  }
}

func WithLabel(v string) ClientOption {
  return func(o *opt) {
    o.label = v
  }
}

func (c *client) New(opts ...ClientOption) *someClient {
  options := &opt{}
  for _, f := range opts {
    f(options)
  }

  return &someClient{options.timeout, options.label}
}

Changes

Adds a new argument type FunctionalOptions

Motivation

This wasn't possible before.

Related issues

Closes #997 #1006

[alameddinc]

I think It should be inserted into the mock library 👍

[dillonstreator]

@nbaztec thoughts on these changes to simplify the signature?

[dillonstreator]

@boyan-soubachov can you please provide feedback on this PR?

[nbaztec]

@dillonstreator The suggestions look good, I've incorporated them.
I was a bit hesitant at first if there could arise a situation during a refactor/upgrade, where the first parameter could be an incorrect type in the assertion, thereby using an incorrect type - but that seems like a non-issue, since the same can happen when specifying a manual string.

[boyan-soubachov]

Thank you :)