separate calcualteScoresheet into calculateTally and calculateJudgeResult + separate tallyFieldDefinitions

[swantzter]

There are instances for mark scoresheets where the order of marks matter in a way that can't be described in a tally sheet. Or times where there are two different schemas used in the mark scoresheet that is easier understood as one in a tally.

This would place the burden of calculating the tally on the judge model instead of as a global helper function (most could still use the global without modification) and change the order of calculation slightly for library consumers:

mark scoresheet => calculateTally() => calculateJudgeResult() => result
tally scoresheet => calculateJudgeResult() => result

and for converting a mark scoresheet for editing in a scoring system you'd use tallyFieldDefinitions (if present, otherwise use fieldDefinitions) and convert the incoming mark scoresheet with calculateTally()