🚸 Enable versioning artifacts based on key akin to the AWS S3 behavior

[falexwolf]

For Artifact, you can now also create revisions by passing the key argument.

We're no longer auto-creating "semantic versions", but make labeling with the semantic version optional.

More intuitive signature because version is gone and is_new_version_of has a more concise name: revises.

before	after

Technical changes:

• 🚚 Deprecate the is_new_version_of argument in favor of revises
• Deprecate passing version to constructors; rather set .version after creating records
• ♻️ Remove auto-incrementing the semantic version tag, auto-increment the ruid instead
• 🚚 Rename is_new_version_of to revises lnschema-core#423

Notion work package: https://www.notion.so/laminlabs/Simplify-versioning-in-LaminDB-8ef6fc7bfbdc44aca7c8dc672d611dc2

Issue:

• Rename is_new_version_of to revises in a backward-compatible way #1831

[codecov]

Codecov Report

Attention: Patch coverage is 94.11765% with 7 lines in your changes missing coverage. Please review.

Project coverage is 92.26%. Comparing base (902769a) to head (53d3446).
Report is 4 commits behind head on main.

Files	Patch %	Lines
lamindb/_artifact.py	89.74%	4 Missing ⚠️
lamindb/_transform.py	83.33%	2 Missing ⚠️
lamindb/_record.py	93.33%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1839      +/-   ##
==========================================
- Coverage   92.33%   92.26%   -0.07%     
==========================================
  Files          52       52              
  Lines        5886     5912      +26     
==========================================
+ Hits         5435     5455      +20     
- Misses        451      457       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

🚀 Deployed on https://66c8cafb551a89915dfedda4--lamindb-qnwk.netlify.app