Separate catch and finally clause types

[frankeld]

Summary

Previously, this rule incorrectly captured more than is allowed. Normally, this isn't a big issue. However, this causes problems downstream because we cannot directly interpret if clauses are catch or finally, and the old version falsely makes it seem like we can have a series of catch and finally clauses.

This version allows:

• At most 1 finally at the end
• 0 or more catch before finally, unless there is no finally. Then, 1 or more catch.

~⚠️ Merge blocked until verification of impact downstream~ No downstream issues

• [x] No increase to real-life code error count
• [x] Tests passed and added relevant tests

Requirements (place an x in each [ ])

• [x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• [x] I've read and agree to the Code of Conduct.

[Nicholas-Lin]

Just curious are there any tests we can add that would have failed with the old grammar but now should pass. Perhaps something like try, catch, catch, finally or try, finally?

[frankeld]

@Nicholas-Lin Not really. The new grammar is strictly more strict, so anything in the new one will pass in the old one. However, I did add a test for multi-clause stuff because it wasn't actually covered.