Allow typedIn to run in replace-with-default mode.

[gianm]

Useful when data servers, like Historicals, are running in replace-with-default mode and the Broker is running in SQL-compatible mode, which can happen during a rolling update that is applying a mode change.

[gianm]

I tested this locally by running a Broker in SQL-compatible mode and a Historical in replace-with-default mode. In this case, the Broker generates inType filters. Without this patch, the Historical threw an error on the query; with this patch, the query ran successfully.

[pranavbhole]

CI is failing due to low branch coverage.

[gianm]

I think we should ignore the branch coverage check here, because the relevant branch is if (NullHandling.sqlCompatible()), which we actually are testing both branches of— just not in the same run.

There were some legit test failures in the non-SQL-compat processing run, which I've fixed in the most recent commit.

[gianm]

The legit failure is fixed; all that's left is the branch coverage failures, which I suggest we ignore.