Don't override antialiasing in markdown
:memo: Mark atom.commands experimental

The CommandRegistry class is still experimental and 404-ing in the
API docs on atom.io
Upgrade to language-todo@0.12
Merge pull request #3610 from postcasio/master

Don't override antialiasing in markdown
Upgrade to apm 0.97
Upgrade to bracket-matcher@0.59
Resolve buildDir before it is used in other join calls
Upgrade atom-keymap
Disable deprecations unless in dev/spec mode

These are currently adding ~200ms to startup so temporarily disable
until the grim performance is improved and/or core and bundled packages
are updated to not call deprecated APIs.
Prepare 0.132
Upgrade command-palette for spec fixes
Add CommandRegistry::dispatch for tests
Don’t clear commands after specs

Commands are typically registered once at eval time. Clearing them
means that commands aren’t available except in the first spec.
Return whether a dispatched command matched a listener
Extract package-manager-specs from atom-specs
Dispatch activation commands with native DOM apis in specs
Restore commands after each spec

This commit adds the ability to get and restore snapshots of command
listeners. Whatever commands are installed before specs begin are
preserved, but commands added during specs are always cleared away.
Allow atom.commands to participate in activationEvents

* Activation events can be handled via atom.commands
* Pre-existing listeners registered via atom.commands are disabled when
  replaying events for the activated package.
Handle dispatching non-existent commands
Forward stop[Immediate]Propagation to original event in CommandRegistry

Previously, stopping propagation would work on the synthetic bubbling
phase of the command registry itself, but the original event would
continue to propagate which is counterintuitive.