browse/origin-search: Ensure to encode origin URL argument in XHR calls
In the origins search Web UI, XHRs are sent client side to get the visit type and status for each found origin. However origin URLs used as Web API URL arguments were not encoded which could result in request errors when an origin URL contain a '?' character for instance.
So ensure to encode those origin URLs used as Web API URL arguments.
Depends on !951 (closed)
Migrated from D8820 (view on Phabricator)