Improve the scalability of reloading Issue Search with a long unsaved JQL character length

Issue Summary

After a certain JQL character length, reloading Issue Search with an unsaved search request will run into an issue with NGINX due to request URI length, preventing successful page load.

Steps to Reproduce

1. Load Issue Search i.e. with 

   https://{TENANT_ID}/issues

1. Switch to Advanced/JQL editor view
2. Type a long valid JQL string (i.e. longer than 6000 characters) and search
3. Refresh the page

Expected Results

Issue Search should ideally be able to handle a JQL string of any length, or disallow such a search in the UI.

Actual Results

Upon page refresh, we receive a 414 status code with no page load.

Failed to load resource: the server responded with a status of 414 (). 

Workaround

Store the long JQL string into a filter, and load/share/export via the filter. This allows us to use the stored JQL without it having to be added to the request URI as a parameter.