[dv/csr] Handle reset in the middle of CSR transactions

The DV code dealing with CSR accesses gets confused if a reset happens while there is an ongoing CSR access. In order to avoid this confusion tests are restricted to avoid resets while there are ongoing CSR accesses. This is undesirable on two accounts:
- It prevents testing IP unit behavior when it gets reset in the middle of a CSR access, which is a pretty realistic scenario.
- It complicates the generation of testing scenarios in order to prevent these cases.

No file or test paths are named. Locate the DV CSR-access handling and the tests that currently exclude resets during ongoing CSR accesses; first reproduce a reset during a CSR transaction. Done means the DV logic remains consistent through the reset and scenarios no longer need to forbid this case.

Written by the indexing model from the issue text.