Fix flaky dependency version retrieval

[sophiewigmore]

Expected Behavior

Dependency workflow version retrieval should work seamlessly.

Current Behavior

The retrieval step fails every few days with a flake, see #336, and the passes again.
It would be great if we could figure out what the issue is and make that code more resilient so we have less toil associated with dependency workflow failures

[ryanmoran]

This appears to be a common issue across almost all of the repos that retrieve from GitHub. We aren't using an API token when we make the request and so in some cases we get rate-limited.

[sophiewigmore]

Some examples of errors I've seen:

1. In Passenger:
   panic: json: cannot unmarshal object into Go value of type []github.GithubReleaseNamesDTO

2. In ICU:
   2023/01/03 12:23:30 received a non 200 status code: status code 403 received

[robdimsdale]

the second failure mode seems entirely consistent with rate-limiting. The first might be unrelated - just a bad response

[ryanmoran]

I think the first case shows up in instances where we aren't checking the status code, so we don't error on a 403 and then try to unmarshal a JSON response that doesn't match our struct and error out.

[robdimsdale]

Also related: paketo-buildpacks/github-config#653

That issue won't cover buildpack-specific dependency code, but it does cover the same types of failure modes in the common tooling.

[robdimsdale]

Also joshuatcasey/libdependency#25 will fix this issue for buildpacks that use libdependency (e.g. passenger)