Taskcluster-taskgraph

Fixed
- `parameters._get_defaults` doesn't fail if `mozilla-repo-urls` didn't manage to parse the URL. Instead, it just provides empty `base_repository`, `head_repository`, and `project`.
- Similarly, `parameters._get_defaults` doesn't try to determine an accurate `base_rev` and `base_ref` anymore. This caused too many issues on developers' laptops. It provides now empty strings too.

Fixed

- `vcs.remote_name` returns the first available remote and warns about it
- `vcs.default_branch` returns the remote branch because the local one may not exist
- `taskgraph.parameters._get_defaults` trims `.git` from project when repository URL ends with `.git`

Added

- `vcs.default_branch` now takes git-cinnabar into account when guessing default branch.

Added
- SSH repositories are now supported in action tasks

Changed
- `run-task` doesn't pull tags from git `head_repository`

Fixed
- `util.time.json_time_from_now()` and `util.time.current_json_time()` now always returns milliseconds instead of sometimes rounding it up
- Trimmed `.git` from tc-treeherder route's project

Changed
- BREAKING CHANGE: `TransformConfig.kind_dependencies_tasks` is now a dictionary keyed by task label.
- BREAKING CHANGE: `vcs.head_ref` was renamed into `vcs.head_rev` to clarify that the function returns a revision. This also matches `--head-rev`.
- BREAKING CHANGE: Similarly, `vcs.base_ref` was renamed into `vcs.base_rev`.
- `run-task` now clones all git-submodules at the same time as cloning the base/head repository.
- `run-task` now checks out a revision as a named branch that matches `${PROJECT}_HEAD_REF`
- `head_ref` parameter now points to a named branch and if needed, falls back to the revision hash

Added
- `vcs.get_changed_files()` which returns a list of files that are changed in this repository's working copy.
- `vcs.get_outgoing_files()` which returns a list of changed files compared to upstream.
- `vcs.remote_name` that tracks the name of the remote repository (e.g.: `default` on `hg` or `origin` on `git`)
- `base_ref` parameter that points to the reference (e.g.: a branch) on the base repository
- `vcs.find_latest_common_revision()` which finds the common ancestor between a provided `base_ref` and the current `head_rev`
- `vcs.does_revision_exist_locally()` to find out if a changeset/commit exists in the locally cloned repository
- `base_rev` parameter that points to the most common ancestor between the ancestors of `head_rev` and `base_ref`
- `register_morph` decorator which does what the name implies.

Fixed
- Regression in 2.0.0: action tasks that created new tasks are now green again. ([99](https://github.com/taskcluster/taskgraph/pull/99)/[#100](https://github.com/taskcluster/taskgraph/pull/100))

Changed

- BREAKING CHANGE: `taskgraph.util.taskcluster.status_task` now returns the status object rather than the string state.
- BREAKING CHANGE: Replacement optimization strategies now take a `deadline` argument.
- BREAKING CHANGE: Replaces `Either` base optimization strategy with an `Any` composite strategy.
- BREAKING CHANGE: `taskgraph.util.WHITELISTED_SCHEMA_IDENTIFIERS` is now `taskgraph.util.EXCEPTED_SCHEMA_IDENTIFIERS`.
- BREAKING CHANGE: The `default` target tasks method now filters out tasks that define a `shipping_phase`.

Added
- A new `taskgraph.util.taskcluster.state_task` returns the string state (like status_task used to).
- The ability to register custom optimization strategies.
- Added `release_notifications` transforms, enabling tasks to send e-mail notifications. It is usually
used in the context of releases when you want to inform a group of people about the completion of
a phase of a release. Notifications can contain data about what project/version reached a given
phase.
- New parameters: `version`, `next_version`, `build_number`. As of now, they are be used by
`release_notification` to send e-mails that can contain such data.