Use named arguments for unreadable function/static/new calls with many null/true/false parameters

[ondrejmirtes]

Refactored calls across the codebase where positional null, true, false, and [] arguments made it impossible to understand what each parameter means without looking up the function signature. Key improvements:

• ResultCache constructor (14 params, 9 consecutive empty arrays)
• AnalyserResult constructor (13 params, 11 empty arrays + false)
• InternalStatementResult/ExpressionResult (false, false, [], [], [])
• DummyParameter/NativeParameterReflection (false, ..., false, null)
• InitializerExprContext::createEmpty() (7 consecutive nulls)
• ClosureType::createPure() (null, null, true, null, null, null, [], [], [])
• IgnoredError::shouldIgnore() (multiple trailing nulls)
• getFunctionType() (false, false)
• narrowType() (false, false / false, true)
• StubValidator constructor calls (true, true, true, false)
• AssertTag/AssertTagParameter (trailing nulls/booleans)
• IgnoredRegexValidatorResult (false, false / false, true)
• FileTypeMapper::getResolvedPhpDoc() (null, null, null)
• ResultCacheManager::restore() / AnalyserResultFinalizer::finalize()

https://claude.ai/code/session_01Tf5zvkNk4w3dp6TU7UM8b6