🔖 Migrations for LaminDB 0.78

[falexwolf]

• add a boolean field .many to Feature that default to True and indicates whether feature values for this feature are expected to occur once or multiple times for an artifact -- something similar for Param

• remove the .transform foreign key from artifact and collection for consistency with all other records; introduce a property and a simple filter statement instead (alternatively, add the .transform foreign key to all other records)

• store provenance metadata for TransformULabel, ArtifactFeatureValue, RunParamValue, ArtifactParamValue

• a boolean on ULabel called is_metalabel to distinguish mere ontological parents from labels that are meant to be used for labeling

• add TracksRun.transform for consistency with Artifact & Collection

• rename run.parent to run.initiator

• given that feature_sets is a public attribute and given that some people might want to query for feature_values or param_values outside the .features and .params managers; we should consider making _feature_values and _param_values public. This will likely also help people better understand the underlying mechanics if they're ever interested. The downside is that then there are two ways to query by a feature or param. If one wants to do nested JSON queries, this could be desired however. We'll need to look into how .params behaves in that regard. 🤔

• introduce a boolean flag on artifact without an index that's either called _store_revisions, which indicates whether revisions are stored; it defaults to True for file-like artifact and to False for folder/array-like artifacts (alternative names: _keep_only_latest or _overwrite_revisions) - see Slack thread

• ? rename Feature to Dimension and FeatureSet to DimGroup

---

Prospective:

• improve Transform.predecessors: https://github.com/laminlabs/laminhub/issues/35