This will make it work regardless of what the current URL happens to be.

Also move the telemetry setting into the options since we might as well
make use of it seeing as how we have to parse it for the base path
anyway.

Also add a description for uninstall-extension and force.

Closes #1417.

By design the disable-telemetry flag does not affect extension
telemetry, only the setting does, so disabling the setting when the flag
is set should cause extensions to also stop sending telemetry.

Fixes #1116.

This allows external services to distinguish between them.

Also add --force so extensions can be updated without prompts.

Closes #1392.

Makes relative paths work correctly.

In Firefox using the gzip mime type will (probably correctly) cause it
not to decompress while in Chromium it still will (incorrectly).

Closes #1379.

To make installing as a PWA possible. Fixes #1181.

Was looking a bit janky with the style changes.

Just sort of winging it.

For #1306.

Also make it a number.

Fixes #1312.

If you want to use the last visited directory you should omit the
directory from the command line.

Fixes #1132.

As best we can, anyway.

Instead of the first.

Should make language packs work again.

It still won't work behind a base path, but if you're using a reverse
proxy you can just redirect to HTTPS yourself. And should probably
handle TLS termination there too.

For sockets I just needed to add back the proxy call.

I temporarily removed this during the refactor so it needed to be added
back. This time I bundled it with the nbin loader code since it's all
related (will also make it easier to remove).

Just display the error message and exit. The stack trace isn't necessary
(since it's likely user error) and is potentially confusing.

- Add VS Code icon
- Trim dashboard to just display dedicated VS Code section
- Version was getting unset during build
- Add back nbin shim which I temporarily took out earlier
- Update tests for log level env var changes

Might fix #1181, although not for the reasons I initially
thought (because the URLs are resolved from the manifest path, not the
path of the current page). This should ensure that the URLs used by the
manifest are always correct regardless of the manifest's path.