create a very simple mb-form-label directive which makes it much easier to manage the display state of form field errors.

basic version of new Database details page using full form validation.  this is a WIP and not complete.

update `defendpoint` to specifically catch ApiFieldValidationException and format the response to include specific field error notes that a client can more easily use.

also updating all of our defannotation calls to use `checkp` and ApiFieldValidationException so that we get our expected output.  updated unit tests accordingly.

* add a new subclass of ApiException called ApiFieldValidationException which is meant to be thrown when there is an issue with the input of an api field that should result in a 400 client error response.
* create a `(checkp ...)` function separate from (check) which accepts a field-name value and throws our new ApiFieldValidationException
* update our `(checkp-with)` macro to use the new checkp function and update a couple lines of code elsewhere to ensure not issues.

tidy up our angular DatabaseEdit controller and remove statically coded values from frontend and pull it via form_input endpoint.

move the Organization admin settings page to a proper submodule under the admin section of our angular app so we are following the same pattern as everywhere else.

don't barf on fields of wacky types like uuid[]

extra try/catch blocks for Sync DB

cast TextFields as texts when getting their length. More try/catches

around DB sync functions

make sure lengths are int's before trying to format

pin to 1.6

"Report Timezone" -> "Reporting Timezone"

add a couple of additional tests for FK syncing

foreign keys shalt be inferred for thy fields when syncing thy DB

Allow setting report timezone at Organization level

update org api endpoints to accept report_timezone value when creating/updating an org + updating unit tests.