Using the Code Search API yields a malformed "next" url

Issue Summary

When using the workspace code search API endpoint and user code search endpoint, the returned JSON object contains a malformed URL under the "next" field. If used as-is, the subsequent query will fail.

Steps to Reproduce

1. Make a standard call against the API
2. Copy the "next" URL and submit a new API call with it
3. Encounter a 404 error

Expected Results

The "next" field should contain a valid URL

Actual Results

The "next" field contains a "&" (ampersand) character after the URI path but before the parameters which is where a "?" (question mark) should be instead, as the question mark is the correct URL delineator.

Workaround

Manually increment the "page" parameter (ignoring the "next" field) or manually alter the "next" field to replace the first "&" for a "?".