fix(public-api): change artifactSequence to artifactCollection in public GQL requests

[tssweeney]

https://wandb.atlassian.net/browse/WB-11598

This is some old tech debt from model reg work. ArtifactCollections should always use the *Collection style not *Sequence.

[codecov]

Codecov Report

Merging #4531 (6e3372d) into main (948e0c1) will decrease coverage by 0.00%.
The diff coverage is 75.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4531      +/-   ##
==========================================
- Coverage   83.12%   83.11%   -0.01%     
==========================================
  Files         259      259              
  Lines       32984    32984              
==========================================
- Hits        27418    27416       -2     
- Misses       5566     5568       +2     

Flag	Coverage Δ
functest	56.95% <0.00%> (+0.02%)	⬆️
unittest	73.27% <75.00%> (-0.07%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
wandb/apis/public.py	82.13% <75.00%> (ø)
wandb/integration/tensorboard/monkeypatch.py	91.35% <0.00%> (-2.47%)	⬇️
wandb/sdk/internal/internal_api.py	89.17% <0.00%> (-0.52%)	⬇️
wandb/sdk/wandb_setup.py	88.44% <0.00%> (-0.51%)	⬇️
wandb/sdk/lib/git.py	79.01% <0.00%> (ø)
wandb/sdk/internal/system/system_info.py	91.55% <0.00%> (+3.24%)	⬆️

[vwrj]

Looks great. Can we add a quick test to make sure that this successfully pulls from a portfolio?

[vwrj]

Nice.

[vwrj]

When this is merged, let's respond to this Github issue here: #4519. We should

• test that the user's code snippet (pulling api.artifact_versions works as a sanity check)
• tell them this will be available in the next SDK release
• create a branch off the currently released version + cherry pick this change on top so that they can be unblocked for their current work until the next release.

There's 2 users who have responded that are using the API to pull artifact versions for the model registry so there must be more out there who have experienced this issue. So I'd like to unblock them as soon as possible.

[tssweeney]

When this is merged, let's respond to this Github issue here: #4519. We should

• test that the user's code snippet (pulling api.artifact_versions works as a sanity check)
• tell them this will be available in the next SDK release
• create a branch off the currently released version + cherry pick this change on top so that they can be unblocked for their current work until the next release.

There's 2 users who have responded that are using the API to pull artifact versions for the model registry so there must be more out there who have experienced this issue. So I'd like to unblock them as soon as possible.

Great - i tested in notebook and it works:

Note: the Artifact::name field refers to the "home" artifact sequence, not the collection in question. To fix this we need to add a new GQL edge that lets us go from artifact version to the membership for a collection.

[tssweeney]

Created a followup PR to fix the artifact version name issue: #4547