…atastore into or-filters

This reverts commit 37400a6.

Adds a new setAncestor method for ensuring only one ancestor is set for the query at a time. This will avoid errors that result because of setting multiple ancestors. Also deprecate hasAncestor because it will lead to warnings like this. Add parser logic to use the value provided in setAncestor for query sent to backend.

Added tests for the query proto, one to make sure the query structure is right when setting ancestor once and one to make sure the query structure is right when setting ancestor twice. Also added a unit test to make sure that ancestor is set the right way internally when using setAncestor.

This code change adjusts the expected result for running an OR query. Old result used to correspond with AND, but now corresponds to OR.

A test is timing out because we are waiting for done to be called. This fix does not require done to be called.

…into or-filters

# Conflicts:
#	src/query.ts
#	test/query.ts

This reverts commit 1159b37.

This reverts commit 86841d6.

This reverts commit e84582f.

This commit is done to avoid a breaking typescript change which could have the potential to affect some users who read `filters` on a query as its type had been changed to be more flexible, but is now back to what it was.

AND and OR should not be static functions of the filter class because then the user has to type Filter.AND instead of AND for example.

Artifacts of having imports laying around and moving functionality between files

This reverts commit bc15f32.

This reverts commit db02a50.

We add additional asserts to the data in order to capture the nuances of the composite operator. For example, for the OR test we make sure the filter doesn’t always require both conditions to be true.

Code for building the `filter` property of the query proto was pulled into the `Filter` object. Comments indicate how legacy functionality was maintained and which lines of code perform which task.

rename new filter to entity filter to eliminate the need for an internal rename that causes confusion

These test cases have mistakes in their names. We should change them to reflect the position of `hasAncestor`.

The name of the base class is now EntityFilter. Adjust this comment so that it correctly matches the parameter type.

rename composite filter functions so that they don’t look like constants and move a map up so that it doesn’t have to be initialized every time.