Upload buildpack_name.zip from URL rather than downloading file locally first.

Please provide details on the following items. Failure to do so may result in deletion of your feature request.

What's the user value of this feature request?
A clear and concise description of what the user value is.

The value here would be speed of uploading the latest buildpacks to the PaaS blobstore.

Who is the functionality for?
Who will use this feature?

PaaS System Engineers / Automated buildpack updates to the PaaS blobstore.

How often will this functionality be used by the user?
How often will they use this feature?

We specifically would use this weekly.

Who else is affected by the change?
Does this feature cause a breaking change? Are other users affected by this change?

Ultimately the buildpacks being uploaded to the PaaS blobstore faster does allow for developers to test changes faster.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

The problem we're seeing here is speed. Whenever we update buildpacks to the latest version weekly, the cf-cli first downloads the buildpack locally (from our internal artifactory instance) and then pushes that local file to the PaaS blobstore.

Describe the solution you'd like
A clear and concise description of what you want to happen.

I'd like an IF condition to be added to the code so that whenever we supply the path as a URL, just have the cli upload those bits directly to the PaaS blobstore instead of first downloading the file locally.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

N/A

Additional context
Add any other context or screenshots about the feature request here.

N/A

No files, tests, or entry points are named. Start by tracing the Cloud Controller path for uploading buildpacks to the PaaS blobstore and determine how a URL is currently handled. Done means a supplied buildpack URL can be transferred without first storing the file locally, with coverage for the new path.