Controller: Make scoring more maintainable

[F30]

Doing scoring thorugh a Materialized View is nice from a DB point of view, however it causes some problems in practice:

• Nobody besides @siccegge really understands the SQL, let alone is able to change it
• Django doesn't know of Materialized Views, so it has to be deployed separately after initial database creation
• The View's current schema is not optimized for rendering the scoreboard HTML, that still requires some processing in Python (see scores() in "calculations.py")

I want something more maintainable, probably more Python instead of SQL.