Use '?' instead of '-1' when running instances is unknown

When the health manager is unable to determine the desired or actual
running instances of an application, the cloud controller will present a
-1 value for running instances to the caller.  This is a relatively
recent behavior change.

To more accurately represent the unknown state, use a '?' in the cli
output for running instances when the value from the cloud controller is
negative.
move Sanitizer into trace package

[#75183186]

Signed-off-by: Joseph Rodriguez <jrodriguez@pivotallabs.com>
integrate with loggregator consumer's SetDebugPrinter

Signed-off-by: Joseph Rodriguez <jrodriguez@pivotallabs.com>
Implement the -o flag on disable-service-access

[Finishes #75741558]
Add translations for enable/disable service access
Refactor Services Plans actor.

[Finishes #76804582]
Fixes output for disabling all plans of a service for an org.

- Also fixes output for a few other cases so that they all conform to
  the same standard.

- Have a pending test in ServiceAccess Suite for story #76553840

[Finishes #75741558]
Update translation files for service-access.
Add bin/gi18n-checkup to bin/test.

[Finishes #76819320]
Add a better return message on disable-service-access no-op.

[Finishes #76553840]
Don't use ruby script for gi18n in bin/test.
Troubleshoot CI.
Revert adding gi18n checkup command to bin/test.

- We already have a CI box dedicated to i18n validation, and this change
  was turning out to be more trouble than it was worth at the moment.

  Perhaps revisit it later.
Refresh auth token on all service-access commands.

[Fixes #76831670]
Stop using deprecated endpoints for domains.

[Fixes #76723550]
Merge pull request #239 from johannespetzold/loggregator-debug-printer

CF_TRACE option for cf logs
Bump goderps
Merge pull request #237 from sykesm/hm-unknown-instances

Use '?' instead of '-1' when running instances is unknown

[Finishes #76461268]
Bump version to 6.4.0
Update CHANGELOG to v6.4.0