Add support for line item options

This adds a foreign key from Transfer to LineItemOptions (as suggested by Jordan in #1119) and updates the accounting controller and StudentExtraCosts module to make use of it.  You can test this by creating new line item types for a program; you can add options (each with a description and optionally a new cost value) from the admin page for the line item type.  You should see each of these options on the extra costs page in student reg, and it should remember your choices when you save and come back later.

Addresses #1119 and #1120.  However, it could be argued that more front-end work is desirable for #1120.  Also, we don't support a combination of multiple LineItemOptions choices and variable quantity (in the StudentExtraCosts module; the accounting controller should be able to handle it).

What is the difference in use case between ```set_preference()``` and ```apply_preferences()```? I see a lot of duplicated functionality (though not even always copy-pasted duplication; the same calculation for ```amount``` is being done in two different ways). The only differences I see is that ```set_preference()``` deletes old state first, and ```apply_preferences()``` takes a list of preferences. Why doesn't the latter need to do deletes? Can the functions be combined, or can the latter call the former? Or is there a specific reason why they both exist?