Web Properties: Audit and provide via web service

The web properties files in InterMine are accessible - somewhat - via web service. We need to review the existing web properties files and make sure we're exposing properties we need to expose, but not exposing things that should be secret. There are four likely paths:

1. This property is already available on the web.
2. This property should never be exposed to the web (example: username, password settings).
3. This property isn't available, but should be - it is, or should be, used in the iOS app, Android app, and/or BlueGenes.
4. This property isn't relevant to anything except the JSPs. It shouldn't be exposed but equivalent properties may be implemented in BlueGenes. (note: if the property is ever likely to apply to more than one UI at once, it _shouldn't_ be in BlueGenes, it should be in InterMine).

Start by reviewing the existing web properties files and how they are exposed through the web service. Compare each property with its use in the iOS app, Android app, BlueGenes, and JSPs; done means every property is classified as exposed, secret, needed by an app, or JSP-only, with the service exposure updated accordingly.

Written by the indexing model from the issue text.