Support https://wiki.php.net/rfc/throw_expression if merged

[TysonAndre]

• Warn about using throw as the left hand side of a binary operator, or for a unary operator
• If possible, make this affect type inference in statements or conditions (is_string($x) || throw new RuntimeException())
• Warn about using the return value $x = throw new Exception(). Until never/no-return is supported, void is probably the best option.

-(throw new Exception())

$condition || throw new Exception('$condition must be truthy')
  && $condition2 || throw new Exception('$condition2 must be truthy');
// Evaluated as
$condition || (throw new Exception('$condition must be truthy') && $condition2 || (throw new Exception('$condition2 must be truthy')));

Other examples from the RFC:

// This was previously not possible since arrow functions only accept a single expression while throw was a statement.
$callable = fn() => throw new Exception();
 
// $value is non-nullable.
$value = $nullableValue ?? throw new InvalidArgumentException();
 
// $value is truthy.
$value = $falsableValue ?: throw new InvalidArgumentException();
 
// $value is only set if the array is not empty.
$value = !empty($array)
    ? reset($array)
    : throw new InvalidArgumentException();

it would help to check if an expression unconditionally throws in UnionTypeVisitor->visitConditional() for the ternary operator and ??