Refactor bundle fields when Drupal core supports code-defined bundle fields

Problem/Motivation

I am creating this issue as a place to start organizing thoughts/considerations around the future of our custom hook_farm_entity_bundle_field_info() and how that will need to be refactored if/when Drupal core adds more official support for code-defined bundle field definitions.

Note that we also started using BundleFieldDefinition fields for Consumer entity fields in #3207716: Use BundleFieldDefinition for additional Consumer fields → .

Related core issue: 📌 Finalize API for creating, overriding, and altering code-defined bundle fields Needs work

Relevant farmOS issues/threads:

• #3175497: [META] Allowing optional/contrib modules to add fields to bundles →
• #3183372: Convert config fields to base/bundle fields →
• #3188055: Provide a hook for adding bundle fields →
• #3192245: Storage is not created for fields created with hook_farm_entity_bundle_field_info until a new entity of that type is installed →
• #3190851: Enable bundle plugins for taxonomy terms →
• #3207716: Use BundleFieldDefinition for additional Consumer fields →

Proposed resolution

TBD

Remaining tasks

TBD

User interface changes

(Hopefully none.)

API changes

(Hopefully none.)

Data model changes

(Hopefully none, other than the mechanism by which bundle fields are defined.)