[FEATURE] Support Vagrant 1.6 version command

Vagrant 1.6 introduces a couple new commands, including the `version` command.
The `version` command shows the currently installed version information and
also checks for new updates available.
[FEATURE] Support Vagrant Share

Vagrant 1.5 introduced Vagrant Share to allow remote access to a Vagrant
environment. This adds support for the `share` and `connect` commands.
[FEATURE] Support Vagrant Cloud commands

Vagrant 1.5 added Vagrant Cloud to share boxes. Some boxes
may be protected, the `login` command allows to access those
protected boxes from Vagrant Cloud.
[FEATURE] Support vagrant global-status

Vagrant 1.6 introduced the `global-status` command which allows
to get a quick overview of all active Vagrant environments for the
currently logged in user.
Improve consistency, remove dots at end of command descriptions
Merge pull request #2787 from irnnr/plugin-vagrant

Support new Vagrant commands
typo, fixes #1806
Minor markup edits
Fixing typo.
Write the update file even if `CLOBBER` is unset.
This is already done in lib/theme-and-appearance.zsh and supports Darwin/BSD/etc
Fix dud alias. Switch --max-depth for just -d

As far as I can tell (tested on Linux & Darwin, BSD man page seems to agree), `-d` is pretty univerally accepted as the depth argument.  So instead of doing a test, we can just use -d and call it a day.
fix(tools/check_for_upgrade): Don't source profile

Reverts #2296, but mostly #1883.

There is no need to source ~/.profile when this script is read. oh-my-zsh writes no configuration data in ~/.profile.

If the user wishes to use data within ~/.profile, then they should source it in another place.

Fixes #2315
Replacing DISABLE_CORRECTION with ENABLE_CORRECTION in zshrc template

Since commands auto-correction must be explicitly enable with
the ENABLE_CORRECTION envvar, this commit replaces the unaccurate
example in the zshrc template.
Defining nocorrect aliases only when ENABLE_CORRECTION is "true"

This commit move the nocorrect aliases definition so they're called
only when the user set ENABLE_CORRECTION to "true" to activate commands
autocorrection.
Ordering nocorrect aliases alphabetically
Fix function/alias naming clash between bower and bundle plugin

Since the `bower` plugin specifies a `bi` alias and `bundle` plugin
specifies a `bi` function, there is a name clash when using both
plugins, which results in the message "Can't 'bundle install' outside a
bundled project" when trying to execute `bower`.

This adresses #2486
Move aliases to 'custom' section of .zshrc template

By convention, user-specific aliases are kept in each user's .zshrc
file. The .zshrc template provided by oh-my-zsh has an area for example
aliases, though these were being loaded before other aliases in libs, plugins,
and themes. As a result, personal aliases could be overwritten by these
other aliases as they are loaded. To make personal customization easier, the
sample aliases section of the .zshrc template has been moved to the area
dedicated for personal customization. This section of the configuration
is processed after all other items are loaded, preventing personal aliases
and exports from being inadvertently clobbered by oh-my-zsh.
extract plugin will unzip *.sublime-package files
Corrected syntax error in github plugin's empty_gh function