feat(artifacts): add save() method on ArtifactCollection to allow persisting changes

[amusipatla-wandb]

Description

• Fixes WB-18464

This PR adds the setter functions for name, type, description, and tags in ArtifactCollection, and adds a save function to persist these changes.

Example usage:

collection = wandb.Api().artifact_collection("type-name", "collection_name")
collection.description = "new description"
collection.name = "new_name"
collection.type = "new_type"
collection.tags = ["tag"]
collection.save()

• I updated CHANGELOG.md, or it's not applicable

Testing

Added integration tests

[codecov]

Codecov Report

Attention: Patch coverage is 98.14815% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 75.86%. Comparing base (fc7b2b5) to head (a128749).

Additional details and impacted files

@@                              Coverage Diff                               @@
##           amusipatla/artifact-collection-pull-fields    #7555      +/-   ##
==============================================================================
+ Coverage                                       75.82%   75.86%   +0.04%     
==============================================================================
  Files                                             500      500              
  Lines                                           54066    54119      +53     
==============================================================================
+ Hits                                            40993    41055      +62     
+ Misses                                          12665    12656       -9     
  Partials                                          408      408              

Flag	Coverage Δ
func	41.45% <31.48%> (+0.02%)	⬆️
system	63.51% <98.14%> (+0.07%)	⬆️
unit	56.37% <31.48%> (-0.03%)	⬇️

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

Files	Coverage Δ
wandb/apis/public/artifacts.py	92.94% <98.14%> (+1.82%)	⬆️

... and 7 files with indirect coverage changes

[ibindlish]

most of the tag-related changes lgtm. just a suggestion regarding the characters that aren't allowed.

[ibindlish]

Approving mainly for the tags part. The rest lgtm too, but might want to check with @estellazx or @moredatarequired since they were involved in the api design. Great work! 😄

[moredatarequired]

Thanks for adding the deprecation! LGTM

[moredatarequired]

I have a mild preference for breaking this up somehow, probably by making smaller private functions for each of the GQL operations. It's up to you though, feel free to merge as-is

[tonyyli-wandb]

Looks good, thanks! Only had one question (with a possible suggestion depending on the answer)

[tonyyli-wandb]

question: may have missed this, so looking to understand first -- is the tag allowed to start or end with a hyphen/underscore (e.g. "-this-is-my-tag_")? If yes, understood -- just wanted to check

[tonyyli-wandb]

suggestion(if-minor): If no, I think the condition/regex may need to could be stricter here -- up to you -- since it'll consider the above example valid. Possible, rough suggestion below:

Suggested change

	if any(not re.match(r"^[-\w]+([ ]+[-\w]+)*$", tag) for tag in tags):
	if any(not _is_valid_tag(tag) for tag in tags):

where:

def _is_valid_tag(tag: str) -> bool:
    split_tag = re.split(r"[ ]+|[-]+|[_]+", tag)
    return all(part.isalnum() for part in split_tag)

[amusipatla-wandb]

good point, it looks like via the UI we're able to start or end tags with hyphens/underscores so I think what we have right now should be fine