silence mass dump of BareExcept when using unittest

[Graveflo]

Seems better to change it to CatchableError instead?

[Graveflo]

At this point I'm thinking that warnBareExcept (semstmt.nim : 353) should have a different name. (semstmt.nim : 397) should probably be silenced unless --legacy:noPanicOnExcept is enabled after RFC 557 was implemented.

[Graveflo]

This seems like the sanest path forward to me. I think asyncmacros needs to catch Exception and so does unittest, so does plenty of other things. It's just a warning right? So then an std module like unittest shouldn't just force it on. That's annoying. People who use it or depend on it for legitimate reasons need to be able to turn that off. As for the name, it seems to have precedence, so just leave it be.

Turned off the "The bare except clause is deprecated" warning when noPanicOnExcept is not enabled as I believe that is wrong now. Unfortunate how that message actually fits the name though.

CI might still fail though ofc.

[github-actions]

Thanks for your hard work on this PR!
The lines below are statistics of the Nim compiler built from cc4c737

Hint: mm: orc; opt: speed; options: -d:release
183330 lines; 7.266s; 661.715MiB peakmem