Normalize comments, variables, etc.

[richburdon]

Prep for #120 and dxos/console#67

To discuss:

• why are only some extensions listed in known-extensions (which data is in this, vs local yml, vs code)?
• cert (why on root CLI)
• forward, mnemonic?
• service (what is this? document)
• machine => kube?
• wns => registry
• peer => merge with mesh
• halo extension (merge with profile?)
• ~/.wire config (migration)
• Typescript (lint)

Moved to: #126

[egorgripasov]

@richburdon We should discuss URL schema changes, and ideally @ashwinphatak and @telackey should also be a part of that discussion.

Main points:

1. Current schema supports arbitrary number of "subfolders", e.g. wrn://dxos/testing/application/egor/arena is a valid app wrn. Question: do we want to restrict to authority:path (e.g. dxos:application)?
2. wrns in app url are urlencoded, because of (1) - because we need to distinguish between wrn itself and file path, e.g. url_encode('wrn://dxos/testing/application/egor/arena')/path/to/file.js
3. Path like dxos:application/console@alpha:service_worker.js not gonna work for bundle files
4. Changes should be backward compatible since migration will take time and would happen on different level of the system.

[egorgripasov]

This is quite artificial for apps, since typically index.html would contain a list of files to use (css, js, ico, etc), so regular GET requests for bundle files would not work that way.

Also, changes like that should be introduced in backward-compatible way, since those convention is used in many places throughout the org, so we can not switch instantly.