🚸 Only auto-search ._name_field on sub-classes of CanCurate

[falexwolf]

Before	After

We're currently using the ._name_field not only as display field, but also to govern auto-search when creating new records.

This isn't meaningful for registries like ParamValue, FeatureValue, Run, Transform, Artifact and others.

Hence, from now on, we only perform the search on sub-classes of CanCurate.

There is a bigger question on when a name field should imply uniqueness (hard on the SQL level or soft via auto-search on the Python level). See more in this internal Slack ref and this issue:

• 🚸 Unique contraint on name field of most registries #2269

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.73%. Comparing base (2a17099) to head (acbaf72).
Report is 22 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2319      +/-   ##
==========================================
- Coverage   92.82%   85.73%   -7.09%     
==========================================
  Files          55       80      +25     
  Lines        7202     8548    +1346     
==========================================
+ Hits         6685     7329     +644     
- Misses        517     1219     +702     

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

[github-actions]

🚀 Deployed on https://677880fd4f3ddf2fde822902--lamindb-qnwk.netlify.app