rvfi_intr.exception is kept high when an exception is followed by a trigger debug entry

Created by: silabs-mateilga

When an exception handler entry is immediately followed by a debug entry with cause trigger, in other words, when the first instruction in an exception handler is a debug trigger hit, rvfi_intr.exception remains high at the retire of the first instruction in the debug handler. The current expectation from verification asserts is that the rvfi_intr.exception signal should follow one retire after rvfi_trap.exception, unless an interrupt is signaled. The question here is if the verification expectation is wrong, or is the RTL implementation wrong?

Reproduce by formally verifying assert ...rvfi_i.rvfi_assert_i.a_sync_cause with latest cv32e40s/dev branch of core-v-verif, at current date.