Update version to 2.0.1 (bitrise-io#830)

Update tool versions (bitrise-io#828)

[BE-198] Forward wrapped bitrise status (bitrise-io#814)

* Forward timeouts from Steps and wrapped bitrise processes.
* Added heartbeat message, this helps avoiding the case where a wrapper bitrise process aborts earlier then the wrapped bitirse process (if both use the same timeout).
* Updated exit codes to less common numbers to avoid confusion with exit codes from shell scripts.

Add support for new property (bitrise-io#811)

* Added support for `no_ouptut_timeout` property
* stepman dep updated

Set CLI version automatically by the release process (bitrise-io#805)

* Set CLI version automatically by the release process

* Define dev version by default, fix tests

Set log level for analytics logger (bitrise-io#799)

* Set log level for analytics logger

* Simplify expression

Implement analytics events for Bitrise CLI (bitrise-io#787)

As a part of our analytics overhaul project we'd like to introduce new
events and robust analytics logging facilities to Bitrise CLI.

- Analytics Plugin is no longer used, events are sent immediately when
  they occur in the background
  - We keep analytics plugin for now and send old events as well
- Events have a hierarchy between them so we avoid property duplication
  also make sure that step events can be connected to their respective
  builds
- Introduced new events for tracking workflow and step execution
  lifecycles better. Added `step_skipped` event to indicate skipped
  steps
- Introduced new state `StepRunStatusCodePreparationFailed` to be able
  to send "real" step failures and step "preparation" failures
- Inputs are sent for all step execution expanded and redacted
- `BITRISE_ANALYTICS_DISABLED` environment variable is used to control analytics behavior

[STEP-1822]

Implement analytics events for Bitrise CLI (bitrise-io#787)

As a part of our analytics overhaul project we'd like to introduce new
events and robust analytics logging facilities to Bitrise CLI.

- Analytics Plugin is no longer used, events are sent immediately when
  they occur in the background
  - We keep analytics plugin for now and send old events as well
- Events have a hierarchy between them so we avoid property duplication
  also make sure that step events can be connected to their respective
  builds
- Introduced new events for tracking workflow and step execution
  lifecycles better. Added `step_skipped` event to indicate skipped
  steps
- Introduced new state `StepRunStatusCodePreparationFailed` to be able
  to send "real" step failures and step "preparation" failures
- Inputs are sent for all step execution expanded and redacted
- `BITRISE_ANALYTICS_DISABLED` environment variable is used to control analytics behavior

[STEP-1822]

updated version (bitrise-io#778)

Add analytics and log message right before the process is finished (b…

…itrise-io#772)

* Add analytics and log message right before the process is finished

* Change message casing

* Prepare for version 1.47.2

* Revert `envutil` remove