Suppressing "NoValue" should not treat subsequent code as unevaluated

[kkmuffme]

Using a slightly adjusted example from https://psalm.dev/docs/running_psalm/issues/NoValue/

https://psalm.dev/r/a1c3c38452

When suppressing NoValue it's clear that there is a value and subsequent code should not treat as if it returned, e.g. UnevaluatedCode, UnusedVariable

[psalm-github-bot]

I found these snippets:

https://psalm.dev/r/a1c3c38452

<?php

/**
 * @return never
 */
function foo() : void {}

/**
 * @psalm-suppress NoValue
 */
$a = foo();

$f = rand( $a, 5 );

Psalm output (using commit 75fcfe3):

ERROR: InvalidReturnType - 4:12 - foo is not expected to return any values but it does, either implicitly or explicitly

ERROR: UnevaluatedCode - 13:1 - Expressions after return/throw/continue

INFO: UnusedVariable - 11:1 - $a is never referenced or the value is not used