If mismatch between property definition and metafield type, fail more gradually

Description

If there is a mismatch between a property definition and a metafield type, the site fails to start, and the message is not helpful to solve problem (until you know about the fix)

This exposes a serious problem when customers uses an external PIM to update the catalog information, and change the meta field type unknowingly. Things like that happen, and we should try to avoid a dramatic failure.

For some sites the current behavior is preferred, as it will make it very clear that there is a fault on the site that needs to be fixed. Some however, prefer more lenient behavior.

So, we should introduce a configuration flag to change the behavior. The current behavior is the default, but if you set the flag, instead of throwing an error, we log it but let the site continue to run.

This change would also make it possible to have the stricter check in test and integration environments, but be more lenient in production.