Fix the CC red build
First pass at making CC work in random order
Log app guid on droplet upload
Fail more descriptively when reaching an app missing condition
Fix flaky test

Change test so it isn't checking right on the boundary of an edge case
updating an app's routes sets a new version

This is so that we can send a new version in dea.update. If the message
is missed, previously the routes being registered would simply never be
updated. This allows the system to notice the receiver (the DEA) is in
an invalid state, and converge properly.

See also DEA commit b622de13d7ad6067bd969dc658f007b7ba6cc4a6.

[#57361124]
fix test that asserted object quality

Really only needed to test presence of the relationship.
Try to get more info when flaky test fails
fix clobbering app updates during staging

There was a race between calling app.refresh and checking if the task is
current, and updating the detected buildpack attribute. It called .save, which
meant any changes that happend between there would get blown away.

This replaces .save usage with .update, which only updates the given
attributes.

[finishes #58774740]
Merge pull request #103 from cloudfoundry/fix-cc-staging-clobbering

fix clobbering app updates during staging
Reject invalid service names before attempt to provision

[Finishes #57270026]
Fix error message for service name invalid.
Move debugger gem to test mode
Removed the actual uploaded file (with the full path rather than just the file name)
Renamed variable name.
[Finish #57819156]
allow creation of shared domains through the API

[finishes #58468508]
Include binding count in service instance summary

User-provided service instances can be bound and thus should include a
binding count in their summary.
querying service tokens by label and provider

[finishes #58586306]
Use expected restcontroller exceptions during authentication.

[Finishes #58573138]
add user cc_user_count to varz end point