[kmac,dv] Extend StKeyMgrErrKeyNotValid state coverage

PR #22794 extended the `kmac_app` module to abort when the sideload key is invalid during operation. When the key gets invalidated during an operation, the FSM inside the `kmac_app` module enters the `StKeyMgrErrKeyNotValid` state. PR #24724 extended DV to increase the coverage of this FSM state. However, still some state transitions into this state are not covered:

Based on PR #24724, the DV test needs to be extended to (_i_) first trigger one of the following FSM error states and then (_ii_) invalidate the sideload key:
```
StError->StKeyMgrErrKeyNotValid
StErrorAwaitApp->StKeyMgrErrKeyNotValid
StErrorAwaitSw->StKeyMgrErrKeyNotValid
StErrorServiceRejected->StKeyMgrErrKeyNotValid
StErrorWaitAbsorbed->StKeyMgrErrKeyNotValid
```
The following state transitions are not covered because of #24739:
```
StAppOutLen->StKeyMgrErrKeyNotValid
StAppProcess->StKeyMgrErrKeyNotValid
StAppWait->StKeyMgrErrKeyNotValid
```

The following state transitions are not covered because it seems not to be possible to enter this state from the origin state:
```
StIdle->StKeyMgrErrKeyNotValid
StTerminalError->StKeyMgrErrKeyNotValid
```

Start with the kmac_app FSM and the DV changes in PR #24724, then trace the listed transitions into StKeyMgrErrKeyNotValid. Extend the DV scenario to trigger each reachable StError state before invalidating the sideload key; account for the exclusions described in PR #24739 and the origin states noted as unreachable.

Written by the indexing model from the issue text.