Improve error message thrown when path is not found

[lizkenyon]

Closes #989

WHY are these changes introduced?

We have seen multiple reports from users who do not know how to resolve the path not found error from the REST resources. This is often due to a required ID not being set.

WHAT is this pull request doing?

Improves the error message to print out potential matching URL paths.

Example error message now:

10:06:07 │ remix │ ERROR Discount RestResourceError: Could not find a path for request. If you are trying to make a request to one of the following paths, ensure all relevant IDs are set.
10:06:07 │ remix │  - price_rules/<price_rule_id>/discount_codes.json

Type of change

• Patch: Bug (non-breaking change which fixes an issue)
• Minor: New feature (non-breaking change which adds functionality)
• Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• I have used yarn changeset to create a draft changelog entry (do NOT update the CHANGELOG.md file manually)
• I have added/updated tests for this change
• [NA] I have documented new APIs/updated the documentation for modified APIs (for public APIs)