FilterSearch updates for builtin.location

[nmanu1]

Update FilterSearch to account for special backend logic when searching on the builtin.location field. In this case, the backend can return filters on builtin.region or address.countryCode as well, so these fieldIds are also considered "matching" for the component. Filters on these fields can be used to populate the input and should be unselected when a new filter is selected from FilterSearch.

J=SLAP-2495
TEST=auto, manual

See that the added Jest tests pass. Spin up the test-site and add static filters on builtin.region. See that they are used to populate the FilterSearch input, warnings are logged, and the filters are unselected by FilterSearch as expected.

[coveralls]

Coverage increased (+0.02%) to 85.72% when pulling 5a135cd on dev/filtersearch-location into f364882 on release/v1.1.0.

[github-actions]

Current unit coverage is 88.8646288209607%
Current visual coverage is 77.78894472361809%
Current combined coverage is 89.51965065502183%

[oshi97]

I was wondering if we'd want to put this weird business logic into headless, since this is the kind of weird business logic that's easy to forget about, but at least right now I'm pretty sure we wouldn't want to do that.

[nmanu1]

I was wondering if we'd want to put this weird business logic into headless, since this is the kind of weird business logic that's easy to forget about, but at least right now I'm pretty sure we wouldn't want to do that.

Yeah, I didn't think we'd want to bake this into headless because it seems to mostly affect the UI for now and it sounds like Product is thinking of making a separate endpoint for this case anyways. I'm not a big fan of having this kind of weird logic in search-ui-react either, but I'm hoping we'll be able to remove it soon and having it higher in the stack will probably make it easier to isolate/remove