add on_map and funded columns to Pd::Workshop

[Hamms]

As the first step in the eventual restructuring of the workshop_type tuple to a pair of bools, captured in this trello card.

Based on this mapping:

	Funded	Unfunded
On Map	Public	N/A
Not on Map	Private	District

Next steps (each in their own PR) will be:

1. Update the controller model to populate these fields for new workshops based on the value of workshop_type, and release a data migration to back-populate already-created workshops
2. Update payment calculations (and anything else not client-facing that examines workshop_type) to rely instead on these fields
3. Remove workshop_type column
4. (after announcement has been sent and documentation has been updated) Update user-facing UI (workshop creation and edit form) to replace workshop_type dropdown with a pair of radio buttons

[Hamms]

@aoby, @ashercodeorg thoughts on this plan of attack?

[aoby]

should these be required (null: false)?

[Hamms]

They will be updated to be so in step 2, as only at that point will we have data for all of em

[ashercodeorg]

It isn't obvious (at least to me) what these columns mean, even after reading the Trello card and your (otherwise nice) PR summary. Mind adding a brief explanation of these fields in this file? Thanks!

[aoby]

Plan of attack SGTM

[ashercodeorg]

LGTM (as does the plan of attack). Depending on how many rows are touched, I'd recommend doing the data changes in a migration (if not many) or a one-off script (if lots).

[ashercodeorg]

It isn't obvious (at least to me) what these columns mean, even after reading the Trello card and your (otherwise nice) PR summary. Mind adding a brief explanation of these fields in this file? Thanks!

[aoby]

RE: column explanations, you can now add column comments, which are stored in the DB.

[Hamms]

There are ~1500 rows in the workshops table, which to my mind falls into the "not many" category.

Edit: actually, there are ~1800 rows, but that still seems like few enough.