Use strict array search

[come-nc]

• Resolves: #

Summary

Without strict:true, array_search has an unexpected behavior with string looking like numbers.

Example:

<?php

$cache = [
	'user1' => '000E01',
	'user2' => '000F02',
];

// All of these calls return 'user1'
var_dump(
	array_search('000E02',    $cache),
	array_search('00E02',     $cache),
	array_search('0E02',      $cache),
	array_search('0E0',       $cache),
	array_search('0E01',      $cache),
);

I splitted in several commits to ease backporting a bit.

The issue was spotted with user_ldap user cache, but all instances of array_search could be impacted with such a corner case so I added strict:true to all array_search calls, apart from object arrays.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

[come-nc]

/backport to stable32

[come-nc]

/backport to stable31