Employ system default TypeSearches where custom is not yet defined in App Resources

[bronwyncombs]

Currently, a custom TypeSearches file in App Resources overrides system defaults. This poses an inconvenience when new typeSearch tables/fields are added since the App Resource must be updated to make new qcbx fields searchable.

It would be much better for the users if there was logic to fill in the gaps of custom TypeSearches files with the system defaults. This is especially beneficial when the schema is expanded and users expect new forms/fields to behave with the system's default search abilities.

The addition of geo, for example, means databases with a TypeSearches file will need to manually configure this for the cojo and taxonTreeDef fields qcbx search to work.