New feature: Database-driven flags and reports on any object (lose the mailto links)

[anildash]

Any place that history is displayed on a product or maker, we should allow signed-in users to flag the action, and have a view to show all flagged actions.

On the flag list view, the flags can be removed by signed-in users. No need for acting upon the flags from that page -- users will just follow the links to fix whatever page is affected, at least until we have versioning.

[ginatrapani]

Prereq: #37 so we don't expose internal IDs, we'll use the new unique hash instead

[ginatrapani]

Few notes on flagging:

• Multiple users can flag an action.
• There will be a "flagged actions" view that displays actions with flags, ordered by most recent flag (I guess)
• A user can archive their own flag.

... Profit? This is completely half-baked at the moment, but what we DO know is there should be a new flags table with a user_id and an action_id and we'll go from there.

[ginatrapani]

Flag object:

• id - internal unique id
• uid - unique id
• creation_time - timestamp, auto-entered
• user_id - int, fkey to users.id
• object_type (action, maker, product) - varchar(20)
• object_id - fkey to actions.id, makers.id, products.id
• report_body - text, user-entered details
• is_archived - int(1) bool

Questions:

• Should we call this object flag or report?
• Should the action of reporting something go into the project and/or maker's activity stream?