Bump ginkgo and gomega
Move loggregator client into consumer library
fix failures in helpers test
Fix log message helper tests
Build binary concurrently during bin/run
Add a datetime for when the binary was built

Part of our CI pipeline for now; apologies for having such an opaque process
into how this works. FWIW the changes to replace-sha are included here as well,
so if you're interested in duplicating this, you shouldn't have much trouble

[Finishes #68515588]
go fmt
Try to fix flaky logs test
Make the time buffer bigger in logs test
GinkgoRecover() in goroutines

This is the only instance I have found, but we should probably
add these in a consistent place.

While these functions look safe, they actually run inside of a goroutine
because of the testhttp package test server implementation. Recovering
makes our errors slightly nicer.
Allow 'cf unset-env' to remove the last env var an app has

Apparently we were a little too defensive when we changed this code to
only sometimes send environment variables. When the env var map has
zero entries, we may want to send that to CC, eg: when an app has
a single env var and we want to delete it

[#Finishes #68879028] #134
go fmt
Add a warning to tests that require cleanup

We have known for some time that our tests were in a bad condition, but
it was not clear to us until we grepped around the source code to see how
many tests had not been cleaned up yet.

Our intention here is to provide contributors some better examples of how
we think Ginkgo tests should be. Hopefully this clears up some of the
confusion
Ignore mercurial .hg directories
Make create user command idempotent

[#67241604]
Replace ServiceInstanceAlreadyExists -> ModelAlreadyExists
Remove disclaimers from some great, great tests
Get rid of some manual json string concatenation
adding pagination to api calls
adding test cases