Require ids in find methods

[paulomarg]

WHY are these changes introduced?

Closes #756

When all ids evaluated to falsey values in the REST resources' find() methods, we could end up defaulting to the non-id specific versions of a request - e.g. /products/<id>.json became /products.json because we treated these ids as optional.

However, typically in REST APIs, whenever we are GET-ing a specific item you'll need to supply its id, so it didn't make sense for find() to do an id-less query.

WHAT is this pull request doing?

Making it possible to trigger an error if we're missing an id by passing in a parameter to baseFind, and updating all find() methods to pass that parameter in.

I'm considering this a bug fix because those requests were never supposed to be fired in the first place and would cause unpredictable behaviour.

To review the "manual" changes, use this link.

Type of change

• Patch: Bug (non-breaking change which fixes an issue)

Checklist

• I have used yarn changeset to create a draft changelog entry (do NOT update the CHANGELOG.md files manually)
• I have added/updated tests for this change

[paulomarg]

Note: I search-replaced the requireIds param in the actual classes, so they should all be the same. Just skimming that code should be enough.

[sle-c]

LGTM, confirmed that .all methods have requireIds: false 🙇