Also make sure it doesn't get committed with secrets

Fix a bug where checkboxes would cause validation errors because marketo
expects a csv serialized field for checkboxes. Has to be handled in the
data mapping because these are custom/dynamic/addition properties so the
library doesn't understand the schema and the mapping at least has some
understanding of the data.

Include error message to site admin can debug form submission failures.

Help users setup contact module by providing a warning when trying to
configure a form but there are no enabled fields to map.

These "work" in Drupal 10 so marking them as ready and bugs can be
handled in follow ups

Constructor doesn't capture additional fields so this was broken.

Some of these empty checks are on miss-documented fields. Update baseline to
silence them for now. Inline supression's would probably be better though.

Some of these fix some changes in user activities I missed.

Some of these are fixes for the 2.0 library branch that has stricter
type handling.

Split the different actions into manageable tabs with singular purposes.

Seems the code triggering this is happy now?

Marketo doesn't really do numeric keys so it is very unlikely to work
the way you want.

This didn't work... then it did. So hopefully it continues to.

Also work around for marketo-rest packagist being broken.

Seems some things are changing to support DrupalCI testing. Cool!

Code generation rewrites the arguments in a weird way so they don't
match 1:1 with the documentation unfortunately.

Still bearish on some of these non-lead properties on the lead object
but this one might be useful in multiple contexts

Makes logic easier to read and provides extension points for developers
that want to try and write custom extensions of this logic. Maybe a
thing because marketo's database can be very business specific.

Hey look... a undocumented and breaking "feature" ...

Relates to #3258450