feat: add context.query() to nock back

[stephenprater]

When TDDing using Nock Back you're kind of in a Chicken-and-Egg situation. You want to be able to verify the external calls you need to make - but you don't know the exact nature of those external calls. This lets you list the interceptors created in a given fixture to make sure all the ones that you expect are there.

By itself, this functions as a negative expectation - like I can verify that certain calls do NOT happen in the fixture. When paired with assertScopesFinished this can be used to verify the complete set of calls in the fixture. For instance I have a fairly complex HTTP interactor that synchronizes a local data store with a remote one. I know how many calls this takes - and I know that if the scopes in the fixture complete then my interaction worked.

But if I need to re-record my interaction, I need to go over to the fixture and check it manually. This lets me make assertions about what is in the fixture - so that I can re-record them and verify that they still do what I expect.

Example Code Simplified and Anonymized to the Point Of Inaccuracy:

it('#synchronize - synchronize with the external API', async (localState) => {
  const { nockDone, context } = await back('http-interaction.json')
  
  const syncronizer = new Synchronizer(localState); 
  
  sycnronizer.syncronize();
  
  nockDone();
  
  context.assertScopesFinished();
  
  expect(context.query()).toEqual(
    expect.arrayContaining([
       expect.objectContaining({
           method: "POST",
           path: "/create/thing"
       }),
       expect.objectContaining({
          method: "POST",
          path: "create/thing"
      })
    ])
  );
})

[gr2m]

Looks good to me 👍🏼 could you please update the README as well to mention the explain the new .query() feature and its use case?

[gr2m]

Thank you!

[github-actions]

🎉 This PR is included in version 13.4.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀