VIVO-84 Use language filtering on the display model

This doesn't answer the questions:
1) How do we edit new pages or existing pages?
2) What is the generalized procedure for adding another language?
template changes for internationalization -- replaced displayed text with calls to properties file containing actual strings
removed values that have yet to be translated
updated the adjustFontSize function to include more checks
the startupStatus-displayRaw template does not have access to the i18n freemarker variable, so backing those changes out
more template updates for i18n
initial work on VIVO-60 application ontology support for property/range combinations
initial work on VIVO-60

Merge branch 'develop' of https://github.com/vivo-project/Vitro into develop

Conflicts:
	webapp/src/edu/cornell/mannlib/vitro/webapp/dao/jena/VClassDaoSDB.java
adding license tag to ApplicationConfigurationOntologyUtils.java
VIVO-87 First attempt at a caching filter.

Appears to work with Firefox cache and Chrome cache, except for language-dependent stuff.

Is that because it isn't configured correctly, or is it because Firefox and Chrome aren't attempting to keep more than one version of a page in their caches? Even if they do see a "Vary: Accept-Language" header?
VIVO-82 Refactoring WebappDaoSetup to clarify the model setup.
VIVO-82 Split WebappDaoSetup into ContentModelSetup and ModelMaker setup.
VIVO-82 Use ModelAccess to get or set the Display Model
VIVO-82 Use ModelAccess to get or set the UserAccounts model
VIVO-82 Use ModelAccess to get or set the JenaOntModel (Union Full model)
VIVO-82 Use ModelAccess to get or set the JenaOntModel (Union Full model)
VIVO-82 Use ModelAccess to get or set the JenaOntModel (Union Full model)
VIVO-82 Use ModelAccess to get or set the BaseOntModel

a.k.a the Base Full model, or AssertionsModel
VIVO-82 Use ModelAccess to get or set the BaseOntModel

a.k.a the Base Full model, or AssertionsModel
application ontology work