Audit `throw 0` instances throughout the code base

[SaswatPadhi]

CBMC version: 516f109

Forking off from @martin-cs's recent comment: #6249 (comment)

We use the throw 0 at several places throughout code base. We should use audit these instances and:

1. check if it would be more appropriate to raise an INVARIANT violation,
2. throw exceptions or at least std::strings in place of 0

[NlightNFotis]

I'm all for this (and would be happy to assist with that effort myself).

We had already done a round of this, around 2018-2019, and we have removed most (all?) of the throw 0;s in some folders, but of course I've seen more of them get introduced over time, and we didn't get through all the project subfolders the first time.