#110486Debugger does not mark the first blacklisted class as filtered
Description
When a class is the first entry in `DebuggerUtility`‘s class blacklist, its
contents are filtered correctly, but the rendered object header is not marked
as `filtered`.
The header currently searches for the class name in an imploded blacklist and
checks whether its position is greater than zero. A class at the first position
therefore fails this check.
Steps to reproduce:
1. Dump an object using `DebuggerUtility::var_dump()`.
2. Pass its class as the first or only entry in `$blacklistedClassNames`.
3. Observe that the object’s contents are hidden, but its header lacks the
`filtered` marker.
Expected result:
The header is marked as `filtered` for every blacklisted class, independent of
its position in the blacklist.
Actual result:
The first blacklisted class is not marked as `filtered`.