Ensure sub-field enabled Drupal fields are populated on ECK entities

In https://gitlab.com/consensus.enterprises/clients/envision-recycling/logistics-app/-/issues/208 we are seeing Date fields that aren't being populated by our steps, apparently because they have subfields. This also seems to be happening for Address fields.

TODO:

• Create new test module with an example ECK type that has Date field
• Create new test module with an example ECK type that has Address fields
• Create a test that shows the failing behaviour for Date fields
• Create a test that shows the failing behaviour for Address fields
• Find the source of the failing behaviour and fix it 😄

See:

• Our code where we create entities: https://gitlab.com/consensus.enterprises/misc/behat-drupal-context/-/blob/main/src/Context/Traits/EntityBaseTrait.php#L47
• Drupal Driver code we call upstream: https://github.com/jhedstrom/DrupalDriver/blob/master/src/Drupal/Driver/Cores/Drupal8.php#L498
• Drupal API call to create entities: https://api.drupal.org/api/drupal/core%21lib%21Drupal%21Core%21Entity%21ContentEntityStorageBase.php/function/ContentEntityStorageBase%3A%3AdoCreate/10