Activate strict FFI

[guillep]

FFI callouts should (unless told otherwise) specify the types for all call arguments.
Otherwise this leads to ambiguities that the FFI engine cannot correctly state:

what is the type of 0? signed or unsigned? 1, 2, 4 or 8 bytes long?
what is the type of 1.5? a float or a double?
what is the type of self?

When the strict mode is disabled, types are inferred, and code will execute mistakenly in many cases.
Important: This could lead to crashes.
Instead, the strict mode just throws an exception when this happens.

Notice that this option can be disabled locally per library (just redefining the options method), but I strongly encourage people to fix their lib bindings instead of using the non-strict mode.

Regarding adoption in the Pharo core IDE, we should check if this works as is, or if we should disable it momentarily for some of the libraries used internally in Pharo (e.g., SDL) that would prevent us migrating.

However, this cannot be integrated yet as SDL has some functions that are not properly mapped

FFICallout>>unsupportedUntypedLiteral:
FFIStrictResolutionMode>>resolveUndeclaredTypeForArgument:withResolver:
FFICallout>>resolveUntypedArgument:
[…]
SDL_Texture(Object)>>ffiCall:
SDL_Texture>>lockPixels:pitch:
[…]
OSSDL2FormRenderer>>updateAreas:immediate:
OSWorldRenderer>>updateDamage: