feat(useFetch): Add query option

[bkeepers]

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

---

Description

This adds a query option to useFetch that will append query parameters to the URL. This is particularly useful for GET requests, which don't currently have a way of including a dynamic payload like POST, PUT, etc.

Query parameters

useFetch accepts query option to generate URL query params automatically from an object. query object can also work with existing query parameters in the URL.

useFetch('https://my-api.com/users', { query: { sortBy: 'username' } })

// Object query will be merged with existing query in the URL
useFetch('https://my-api.com/users?q=john', { query: { sortBy: 'username' } })

Replaces #3191, which is a little outdated and has merge conflicts. cc @jd-solanki
Closes #3183

[ilyaliao]

Based on the discussion in #586, perhaps we should reconsider whether this feature is necessary.