Deploy pages using artifact IDs

[konradpabjan]

Closes: https://github.com/github/actions-results-team/issues/1988

Currently deployments are made using and artifact_url. This is done so that internally we call APIs while a run is still in-progress which is a big limitation with the current v1-v3 artifact actions. With the upcoming v4 artifact actions as soon as an artifact is uploaded then it is immediately available from the Artifacts API. The public API will allow us to work with artifact IDs which are much cleaner then working with a artifact_url.

As part of the changes I did the following

• Add a new getArtifactMetadata method that fetches artifacts for a workflow run given a run ID and name
• Remove all the old code that dealt with fetching the current artifact_url
• Remove 3 packages that are no longer needed
• Update all the existing tests
• Add some new tests specific for artifacts

See this example run: https://github.com/bbq-beets/testing-artifacts-v4/actions/runs/6697548931/job/18197689133

It fails as expected because the code downstream in the API is not ready to handle an artifact_id. This is being worked on now in a subsequent PR internally.

[TooManyBees]

Looks good. Though let's make a compatible PR for the API before merging this.

[konradpabjan]

End to End deployment with artifacts V4 now works! We can merge this in 😃