fix: show user logout reason message

[ryan-willis]

I noticed that there's a message attached to the app URI when a session expires:

[main] Open Deep Link URL insomnia://app/auth/login?message=Your+session+has+expired.+Please+reauthenticate+to+continue+using+Insomnia+Sync.

Here's the result of the change:

I also included the ability to specify a custom timeout for fetch calls to the API; it's not in use right now but was helpful when debugging some connectivity issues

[jackkav]

Timeout: I see no reason not to add the timeout option but we should take caution before modifying it in production as it can contribute to outage conditions.
localStorage: Since we don't persist any other x-insomnia-command contents to locaStorage what the rationale to start doing it in this case? Can we make that clearer from the implementation?

[jackkav]

we have a useLocalstorage.ts file containing this hook

[jackkav]

I just noticed its also deleting after reading, which make its it different to the hook.

[ryan-willis]

@jackkav

localStorage: Since we don't persist any other x-insomnia-command contents to locaStorage what the rationale to start doing it in this case? Can we make that clearer from the implementation?

The rationale was to imitate prior art: we persist contents to localStorage in the /app/open/organization case at the end of the switch block, which has the same pattern where a temporary value is set in localStorage, then removed later.
https://github.com/Kong/insomnia/blob/develop/packages/insomnia/src/ui/routes/root.tsx#L218
https://github.com/Kong/insomnia/blob/develop/packages/insomnia/src/ui/routes/organization.tsx#L282

The other method I thought of was to pass parameters through the /auth/logout action function, so if that's a better pattern to follow or clears up the intent I can make that change

[jackkav]

not generally encouraged to use default args in this codebase, as we prefer fallbacks defined in the logic where we can co locate them with other fallbacks or logic. onlyResolveOnSuccess is an exception, I'll see if there is a way to avoid these