Convert integers (like created/updated) to timestamps if mapped to date fields in Salesforce

\Drupal\salesforce_mapping\SalesforceMappingFieldPluginBase::pushValue is supposed to handle this, so let's consider this a bug.

Also, see past discussion on 🐛 Mapped date fields are not properly syncing data. Closed: outdated

Shoot, I didn't find that open issue! That's the same issue as this one in my opinion, although the patches there only deal with pushing. @AaronBauman I'm fine with closing this as a duplicate and moving patching over to there, if it's ok to also work on pulls in that issue too?

i think it's fine to keep both issues open, as that one has a lot of baggage already and is tagged on 4.x

I created the patch to transform SF data to the timestamp for created/changed value.

keopx → changed the visibility of the branch 3382005-convert-integers-like to hidden.

Looping back around on this one.
AFAIK this MR addresses an impossible scenario - a "datetime" field from salesforce whose data is getting pulled as an integer.

Salesforce stores datetime values as strings in iso8601 format, which is what the current \Drupal\salesforce_mapping\SalesforceMappingFieldPluginBase::pullValue method checks for.

Maybe what we want is for the module to be aware of the Drupal field type and cast an integer value from Salesforce accordingly. That's a much bigger can of worms (ie. what other mis-matched field types do we want to support?), and not addressed by this MR as best I can tell.

The attached patch adds timestamp value push support by converting timestamp into supported by Salesforce format.

The code originally from the last patch in old discussion branch https://www.drupal.org/project/salesforce/issues/3122412#comment-14116705 🐛 Mapped date fields are not properly syncing data. Closed: outdated ,
additionally fixed bugs
- 'date' salesforce type converting
- possibly missing requested drupal field definition (due to 'drupal_field_value' may have not a drupal field name value)

Tests coverage still needed.