Update workflows and actions to create and upload pURL field for dependencies

[ForestEckhardt]

Background

Based on the conclusion from the investigation which can be seen in #42 , all buildpack dependencies should have a pURL as part of their metadata on the dep-server.

Implementation

• Update action to generate a pURL for all of the dependencies currently served by the dep-server
• Update the workflows to include this metadata as part of the upload
• Backfill all of the existing dependency entries with pURLs
  • bundler
  • composer
  • curl
  • dotnet-aspnetcore
  • dotnet-runtime
  • dotnet-sdk
  • go
  • httpd
  • icu
  • nginx
  • node
  • php
  • pip
  • pipenv
  • python
  • ruby
  • rust
  • tini
  • yarn

Acceptance

This story is complete when the following conditions are met.

1. A pURL is generated for all dependencies by an action each dependency when it is built during the build-upload workflow.
2. The existing test-upload workflow upload the pURL to the dep-server successfully
3. All of the dependencies/versions of each currently served by the dep-server have pURLs in their metadata when we go to the dep-server url.

[ForestEckhardt]

Blocked on #83

[sophiewigmore]

Unblocked on #83 now it has been completed

[sophiewigmore]

Done in #89: Update action to generate a pURL for all of the dependencies currently served by the dep-server
Done in #89: Update the workflows to include this metadata as part of the upload

[sophiewigmore]

TODO:
fix up icu, and make sure all dependencies have well-formed purls.