Issue title: Switch from paketo-community Ruby Buildpack to paketo-buildpacks Ruby Buildpack
 Issue body: **Is your feature request related to a problem? Please describe.**
Hi from the Paketo team! We've [recently promoted](https://github.com/paketo-buildpacks/rfcs/blob/master/accepted/0005-ruby-promotion.md) the Ruby Buildpack from a community buildpack to an official Paketo Buildpack. 

As a part of this change, the buildpack ID has been updated from `paketo-community/ruby` to `paketo-buildpacks/ruby` and buildpackage artifacts will get published to `gcr.io/paketo-buildpacks/ruby`

**Describe the solution you'd like**
Please start consuming the latest Ruby Buildpack with ID `paketo-buildpacks/ruby`. The existing location (`gcr.io/paketo-community/ruby`) will continue to work, but you will need use `gcr.io/paketo-buildpacks/ruby` in order to continue receiving buildpack releases

 Comments: 
 Comment 0: We have created an issue in Pivotal Tracker to manage this: 

https://www.pivotaltracker.com/story/show/175065881 

The labels on this github issue will be updated when the story is started.
 Comment 1: @paulcwarren I think we can close this? I see this on the latest version of CF for K8s
 Comment 2: Delivered in 1.0
{'source': 'GithubIssues', 'repo_name_with_owner': 'cloudfoundry/cf-for-k8s', 'issue_id': 712263929, 'repo_stars': 306.0}