Use strict mode for "in_array()" functions in "\Drupal\serialization\Normalizer\NormalizerBase" for verifying supported types for (de-)normalization

Follow up for #2863778-19: Clean up \Drupal\hal\Normalizer\NormalizerBase: duplicate less from the parent class \Drupal\serialization\Normalizer\NormalizerBase → :

@BR0kEN - it's the lack of the third argument and it not being TRUE that scares me. Pretty much people always want in_array($needle, $haystack, TRUE) and not in_array($needle, $haystack) - see https://3v4l.org/sr29Y

Problem/Motivation

Normalizer could define type(s) of data which they wants to normalize using supportedInterfaceOrClass property of \Drupal\serialization\Normalizer\NormalizerBase. The same available for request types, which are accepted by normalizer (using format property).

In both cases these properties will be casted to an array to be handled by in_array() function to find the matches and, in both cases, this will happen without strict data comparison which could cause potential inconsistences.

Proposed resolution

2. Add tests