The JS model for a JS view for a config form was previously rendering

incorrectly (without a trailing )). This issue has been addressed.

Also, we now are more careful to only render a trailing comma after the

JS model data if there is in fact a page-wide config object. This object

is now only added to the models if it exists.

Tested this with Review Board. The generated JS works now.