Implemented Bulksettings page & Tests

From Jane's Story: 

@jinpa @jrbl @nparlante 

"Proposal: We propose to build a utility which lists, for each problem in the course, its "settings", as well as some of the information it inherits from its Subsection, namely: Due Date, Release Date, Grading Type.  Each problem's title can be a link to the Studio page for the unit that the component is a part of, so that if a user spots something on the page that needs editing, they can quickly navigate to the where they can edit it.  Later on, we may make settings editable in-place on this page, perhaps even in bulk, but that won't be part of this release.  "

![screen shot 2014-07-11 at 12 04 27 pm](https://cloud.githubusercontent.com/assets/3598201/3557314/43dd1282-092e-11e4-8e9c-8fc4f6f95155.png)
![screen shot 2014-07-11 at 12 04 14 pm](https://cloud.githubusercontent.com/assets/3598201/3557313/43d0a4ca-092e-11e4-9af0-e4bf7be9c235.png)

Nice. If computed_settings_data is expected to be something like an empty dictionary, you could make a stronger statement (while documenting your expectation) by checking for equivalence with {}.