Propagate form_label name to the UI navbar

[signebedi]

The navbar does not currently use the form_label field. It makes sense; to access it, we need to (under current logic) render the full form model / config. Instead, we might want to create a macro called get_visible_form_names() that return a key-value pair between the form config name (eg. not necessarily human readable) and the human readable form, which defaults to a title-case rendering of the form name but can be overwritten by the form_label field.

Originally posted by @signebedi in #367 (comment)

[signebedi]

What this issue doesn't do: it does NOT propagate the form label across the application. There are plenty of places where the default form name is being used and not being masked by its label. Eg. All the read/search pages, esp. those with datatables.

[signebedi]

Propagate form_label name to read/search UI pages
This needs to be extended to mask instances of the form name where we can / where it makes sense. There are some places where I imaging we will not want to use the label... It can be easily accessed in the Jinja2 as visible_form_names[form_name], which can replace references to form_name that replace the underscore with a space...