feat: mock as object syntax

[AndersDJohnson]

Allow mocks to export an object syntax instead of nested arrays (and let mockyeah.get(), etc. accept these as a single argument), e.g.:

{
  match: 'http://example.com',
  options: {
    text: 'ok'
  }
}

or perhaps (maybe also):

{
  request: 'http://example.com',
  response: {
    text: 'ok'
  }
}

or:

{
  req: 'http://example.com',
  res: {
    text: 'ok'
  }
}

Use programmatically:

mockyeah.get({
  match: 'http://example.com',
  options: {
    text: 'ok'
  }
});

Use in mock suite:

module.exports = {
  mocks: [
    {
      match: 'http://example.com',
      options: {
        text: 'ok'
      }
    }
  ]
}

This wrapping object would allow us to add metadata to the suites or make it extensible for other options in the future, such as a description, a default latency or other settings per-suite, e.g.:

module.exports = {
  description: "This suite does things.",
  latency: 1000,
  mocks: [
    {
      description: "This mock does things",
      match: 'http://example.com',
      options: {
        text: 'ok'
      }
    }
  ]
}

Or perhaps (optionally) more simply, just an array of objects:

module.exports = [
  {
    match: 'http://example.com',
    options: {
      text: 'ok'
    }
  }
]

See also single suite option #410, and suite files as JSON #414.