Better detect when Livebook runs out of memory on install

[josevalim]

On machines with low memory, it is most likely installation will fail. We can try to detect those scenarios and show a message to the user when it happens.

In a nutshell, the idea is to change the URL when installing to add a parameter. The parameter can store information such as the current node identifier (randomly generated) and the current timestamp. If the app restarts, we will try to join the same URL and redirect because the session does not exist. If that's the case we can and

1. there are no sessions
2. the node identifier in the parameter does not match the current node
3. Node.list == [] is empty
4. and it has happened within 150 seconds

We can then show an error message saying the notebook belonged to another Livebook instance and it most likely crashed during installation. We mention installation may be expensive and a larger machine may be necessary.

[ByeongUkChoi]

How can I detect when Livebook runs out of memory on install?

[josevalim]

Unfortunately it is not really possible to detect, and that's part of the problem. I pushed an attempted solution here #2128 .