[fix #182] Show Warning In-line for Windows Gems

When deploying a Gemfile.lock that has been generated via windows, we must remove the file which can cause bundler to not be able to resolve.

When bundler does not resolve, the end user never sees the windows warning message due to the resolver never finishing (since warnings are saved until the end of the output).

This change allows warnings to be emitted inline and changes the default behavior of the windows warning to display before the `bundle install` is run, thus mitigating this problem.

Even when the `bundle install` fails the warnings are not displayed since the process `exits` rather than continues to print out the warnings.

Here is a link to the devcenter article I wrote for this PR https://devcenter.heroku.com/articles/bundler-windows-gemfile
If a manifest file was detected skip rake detect

When a user is deploying with a manifest, we don't not need to load up their Rake to see if they have the `asset:precompile` task. Changing the order of the checks prevents users from seeing debugging information that is not needed and helps speed up apps by doing less work.
[ci skip] changelog
extract the BUILDPACK_VERSION into it's own file
setup path so requires work when just requiring language_pack
rake task to increment BUILDPACK_VERSION number