convert old Reasons db entries to Comments db entries

[michielbdejong]

Maybe also merge Update Status into Edit Point?
And add a rule that even a curator cannot approve their own points.

[michielbdejong]

also, remove rating field from point, since it comes from case.
and decide if points should go back from approved to pending state if their details are changed:

• case_id (obviously)
• service_id (obviously)
• custom title
• custom description (but careful not to create conflicts with @madoleary's unmerged changes - asked her about this on Signal)
• quote-{Doc/Rev/Start/End/Text}

[michielbdejong]

Also need to think about peer-review of changes to for instance case title, service url, and other edits outside the points table.

[michielbdejong]

maybe we can use the news feed on the home page, so people can approve each others' changes, and add a new change to revert if disputed. we can then manually check that there are no unapproved changes when deploying.

[michielbdejong]

the merge was done, now i changed the title for the remaining task of doing a small db migration so that we create one Comments table entry for each old Reasons table entry, and then drop the Reasons table (as well as the Points.point_change column) from the db schema.