Tab-away from app/browser then tab-return to browser causes estimate forms to resubmit, triggering a new network request.

[mattburnett-repo]

This shouldn't happen. Once a form is submitted, it shouldn't re-submit if the user tabs away from the app/browser and then tabs back into the app/browser.

The code currently passes the form's requestData to useQuery()'s queryKeys array, but this doesn't consistently solve the problem. Sometimes it works, most of the time it doesn't. No idea why.

Not sure why this happens. The assumption is that the queryKeys will cache the query and prevent a re-render / re-fetch of the Estimate component. This does not work consistently.

useMemo() might solve this. Need to figure out if / where / how.