This commit adds support for adding dimensions to existing
fields. Values and human readable values (optional) can also be
added/updated.

In some databases (i.e. Oracle) query responses can contain different
datatypes than what the JSON can support (the encoding for the values
column of the field values table). This commit adds a funciton that
transforms the values from the field values table to the format the
database will return.

This commit fixes an issue with Oracle when using remapping, with a
column name that is ambiguous and a limit. Those queries are wrapped
in another query, which will fail in Oracle due to the ambiguous
column name. Columns will not be re-aliased if they collide in Oracle
to prevent this issue. Most of this code was written by
@camsaul (Thanks Cam!).

Previously when java.jdbc renamed a project column (i.e. NAME to
NAME_2) to disambiguate them, we would discard previous information on
that NAME column and reconstruct it based on the data that comes back
from the query. This changes that behavior to update the existing
column data to the new name. When we do not have metadata on that
column it will use the existing behavior to infer that.

This commit also adds some tests for remapping which uncovered this
bug.

This moves values to be nested under the related fields object, and
includes dimension along with human_readable_values in the field as
well.

This commit just defs a map with a default map of key/values for
fields/placeholders/columns and merges that with a map of what's
different for that test.

Fixes up eastwood warnings, add docstrings to public functions

This commit adds logic around an FK remapping found in the
dimensions table. It will follow a foreign key to the related
table and use the indicated column from that table as the remapped
value for the source column.

This commit also switches the "remapped_from" and "remapped_to"
attributes returned in the query response to use the "name" of the
remapped column as there could be ambiguity with the previously used
display name.

This commit splits the what was the expand-resolve middleware separate
expand and resolve middlewares. This also splits the source table
resolving to a separate middleware. This split sets up being able to
add an FK field after query expansion to be resolved normally as it
goes through the pipeline.

This commit adds storage of dimension data that the user provides for
an existing field. This is to translate enum-like
fields (i.e. integers) to a textual description of that data. This
remapped value will be included in the response with the original
value. The UI will then take that and show the more user friendly
remapped value.

The new "remapped_from" and "remapped_to" attributes in the cols field
of the response will indicate that a field replaces another field.

This is of most use at the REPL when you want to invoke a
function (such as expectations/run-tests) and have the test
scaffolding available and cleanup after itself.

Set appropriate JVM options for E2E tests

Fix Jest OOM errors

Disable E2E tests that are failing / being converted to use Jest&Enzyme [WIP]

Correct indecies to indices in migration file

Nested queries

be less picky about streaming responses in tests

It was expecting an exact number of keep-allive packets, now it just
checks that there are at least two.

Fix LDAP Flow errors

Fix LDAP branch reflection warnings and a few other style issues

LDAP Auth

Fix CI error in bigquery_test