A QoL improvement for `cabal test plutus-core --test-options=--accept`

[bezirg]

Pre-submit checklist:

• Branch
  • [ ] Tests are provided (if possible)
  • [ ] Commit sequence broadly makes sense
  • [ ] Key commits have useful messages
  • [ ] Changelog fragments have been written (if appropriate)
  • [ ] Relevant tickets are mentioned in commit messages
  • [ ] Formatting, PNG optimization, etc. are updated
• PR
  • [ ] (For external contributions) Corresponding issue exists and is linked in the description
  • [ ] Targeting master unless this is a cherry-pick backport
  • [ ] Self-reviewed the diff
  • [ ] Useful pull request description
  • [ ] Reviewer requested

[Unisay]

I understand that you're filtering out the --accept option, but I don't get why? Please help me to understand how exactly this change is QoL.

[bezirg]

I can then just run cabal test plutus-core --test-options="--accept".

Otherwise, I have to run this when I develop:

cabal test  satint-test ndex-envs-test flat-test flat-big-test traceToStacks-test
cabal test plutus-core-test untyped-plutus-core-test plutus-ir-test --test-options="--accept"

or sth like that