VS Code has a short delay before writing storage (probably to queue up
rapid changes). In the web version of VS Code this happens on the client
which means if the page is reloaded before the delay expires the write
never happens.

Storage updates are already promises so this simply returns the promise
returned by the delayer so it won't resolve until the write actually
happens.

Fixes #2021.

This way, building a standalone release locally and putting it in the
release contianer for testing is less likely to break.

Needs to be reflected in the documentation and the dockerhub description now.

Closes #881

Add initial support for opening files / folders in running code-server instance.

Current limitations:

- unable to open a file in a new window, only folders
- unable to use addMode feature
- others...

systemd's user units are buggy on certain versions
and do not linger by default.

Closes #1771
Closes #1673
Closes #1882
Closes #1861

Co-authored-by: Ngiddyuptiger <65830808+giddyuptiger@users.noreply.github.com>

See #1894
See #1892
See #1810

tsc doesn't check if the output exists when incremental is true.

i.e if I delete the out directory, but keep the tsbuildinfo and
try to rebuild, nothing happens cause it thinks everything is
up to date I guess...

With this change, yarn clean will now remove the tsbuildinfo correctly
so things work as expected.

Mostly to match everything else.

Mostly so the base URL resolution code can be shared.

code-server exports its types but they weren't complete since it imports
ipc.d.ts and that wasn't being included.

The updated logger outputs timestamps now.

The broken symlinks cause nfpm to fail.

The postinstall uses rimraf so it needs to exist in the final build.

It can still be used to check for updates but will not apply them.

For now also remove the update check loop in VS Code since it's
currently unused (update check is hardcoded off right now) and won't
work anyway since it also applies the update which now won't work. In
the future we should integrate the check into the browser update
service.

- dashboard
- app api

Fixes #1884.

For some reason it only affects the extension host socket (something to
do with passing it via IPC?) but I changed both just to be sure.

Fixes #1795.

Fixes #1829.

The previous release mistakenly distributed the wrong version
of node...

Very sad.

See https://github.com/cdr/code-server/issues/1710#issuecomment-646472716

Closes #1693