Fix submodule init on clone

In a previous pull request, clone was changed to initialize and update
submodules recursively.  This change used a flag, --recurse-
submodules, that was added after the version of git being used by the
dea.  This flag was actually an alias to --recursive which does exist
in the version of git used by the dea[1].

The fix made for the previous failure was to split the clone command
into two calls (clone, then change directory and initialize
submodules) which was unnecessary.  In addition, this fix added some
logic around cloning with --depth=1 that broke this depth
functionality when cloning with http:// URLs (the default when using
GitHub).

This change has the net effect of reverting the changes in
20bcb31275e1605d626fb1869dc9fb8314252dd0 and doing this simplest
possible fix for the --recurse-submodules change.  Specifically this
change rolls back the changes around --depth=1 as they are not
necessary to fix the problem with the unsupported flag and break the
functionality that --depth=1 was intended to provide.

[1] The options clone supports in the version of Git on the dea

-----> Downloaded app package (23M)
-----> Downloaded app buildpack cache (4.0K)
error: unknown option `recurse-submodules'
usage: git clone [options] [--] <repo> [<dir>]

    -q, --quiet           be quiet
    -v, --verbose         be verbose
    --progress            force progress reporting
    -n, --no-checkout     don't create a checkout
    --bare                create a bare repository
    --mirror              create a mirror repository (implies bare)
    -l, --local           to clone from a local repository
    --no-hardlinks        don't use local hardlinks, always copy
    -s, --shared          setup as shared repository
    --recursive           initialize submodules in the clone
    --template <path>     path the template repository
    --reference <repo>    reference repository
    -o, --origin <branch>
                          use <branch> instead of 'origin' to track upstream
    -b, --branch <branch>
                          checkout <branch> instead of the remote's HEAD
    -u, --upload-pack <path>
                          path to git-upload-pack on the remote
    --depth <depth>       create a shallow clone of that depth

/var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:33:in `clone_buildpack': Failed to git clone buildpack (RuntimeError)
	from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:41:in `build_pack'
	from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:26:in `block in compile_with_timeout'
	from /usr/lib/ruby/1.9.1/timeout.rb:68:in `timeout'
	from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:25:in `compile_with_timeout'
	from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:16:in `block in stage_application'
	from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:12:in `chdir'
	from /var/vcap/packages/dea_next/buildpacks/lib/buildpack.rb:12:in `stage_application'
	from /var/vcap/packages/dea_next/buildpacks/bin/run:10:in `<main>'
send shutdown message when the dea is exiting

this can be picked up by other components (CC, HM) to invalidate the DEA
from their advertisements, and know not to send apps there

[#50233251]
fix specs for new dea shutdown message
Merge pull request #25 from nebhale/50081011-recursive

Fix submodule init on clone
Revert "Fix submodule init on clone"

This reverts commit e27ed0992a75e2dff10eaf163f0c329f8a491059.

The pull request merge caused test failures
Put default staging requirements into config class
DEA publishes can_stage to varz
DEA sends dea tag with its router registrations
Revert "Revert "Fix submodule init on clone""

Clone without depth 1 so it can work with a bare repo that is created as
part of the testing suite.

This reverts commit 677bddfa926b34e0e67ea09d288f563a11f50198.
Specify engine versions in dea test Node.js app
Fix for dea having multiple apps in BORN state when the create message is invalid

[Finishes #50755909]
Change the tag in router.register to be 'component' => 'dea-uuid'
Ensure that the "Staging" logger uses the configured Steno level.
Revert "DEA no longer snapshots it's entire state"

Only saving snapshot is reverted back, loading was removed

This reverts commit 70fdbc8f39e6fad7a8e1468b22d5c624ee129476.

Conflicts:
	spec/integration/running_app_spec.rb
	spec/support/bootstrap_setup.rb
Merge pull request #26 from IronFoundry/staging-task-logging

Ensure that the "Staging" logger uses the configured Steno level.
Dea sends its index instead of its uuid during router.register
Dea passes a Steno logger to VCAP::Component
Add varz attribute for number of available stagers

[#49814623]

* varz["reservable_stagers"]
Add 'available_memory_ratio' metric to varz
Add available disk ratio

Also fix available_memory_ratio implementation

[#49814623]