Update data entry validation for csb

[jschuurk-kr]

Scope

• merge CSO and DSO rules that check the same things
• F.310 also applies for DSO
• change error code for F.360 to be consecutive with the other F.3xx errors
• add rule to check if E is empty or 0 when it should not be
• add rules voor CSB
• check handelingsperspectieven CSO and DSO, esp. for "rubriek 3.3"

Do also check the commit messages for a list of the changes.

TODO

• review of 'handelingsperspectieven' by @lode-coder

Questions for draft PR ✔️

1. Can I proceed with the change to the version that has the table? Or do you have a better idea how to distinguish rules and texts for GSB CSO, GSB DSO, CSB (and later HSB)?
   => table
2. For GSB CSO and CSB CSO we have in some cases the same checks, but different texts for the coordinator. What is a convenient way to handle that in the frontend? Can we just check for committee category? Or should the difference be part of the error/warning code?
   => frontend can check committee category and counting method to determine which text to show for a particilar error code

Questions for review

1. Is it correct that the rules in "Regels voor extra onderzoek en controles (reeks F.1xx)" only apply to first sessions? Since they refer to fields only available on the PVs of the first session, which are not part of data entry for any later session. => @lode-coder suggests it is not applicable.
2. For the rule of number of eligible voters, I added a check if it's empty or 0. We also discussed checking if it's larger than number of 'stempassen' + 'volmachtsbewijzen'. That's a valid but also somewhat arbitrary lower bound, though. So I think we should rely on the double data entry for the number to be correct.
   => We also add a warning when eligible voters is lower than stempassen.

[jorisleker]

Stuk overzichtelijker zo @jschuurk-kr, top!

Paar vooral inhoudelijke comments, deels om ook met Lodewijk te bespreken