Take the selected filters into account, support multiselect filters and make 'delete all' text translatable

I have added a patch from comment 2 to the merge request. Also, made two fixes:
1. Added support for search_api_term filter plugin.
2. Changed selector to exposed-form submit button in JS. I think it will be useful because when the exposed-form is in a separate block submit is a not .

https://git.drupalcode.org/project/views_filters_summary/-/merge_request...

I created DrupalPod, added view with exposed filters and all values are showing up
- link to gitpod https://gitpod.io#snapshot/8102f986-9376-43eb-8b5e-90c19d31e7d7
- url of the view within snapshot /test-3328219?type%5B%5D=article&type%5B%5D=page&field_tags_target_id%5B%5D=7&field_tags_target_id%5B%5D=6&field_tags_target_id%5B%5D=9

Setting as Needs Work as the MR doesn't apply to the newest 2.x version.

Created patch for 2.0 version based on patch from #7

Everything in #11 worked as expected except for the translation of the reset link. Think it also needs a |t filter in the twig.

I've made that small addition in this patch.

I updated the MR13 to better understand the changes from the patch. Needs further testing and review if we are going to use it instead of the patch; just to be sure I did the rebase correctly.

As for the patch provided in #15 🐛 Take the selected filters into account, support multiselect filters and make 'delete all' text translatable Needs review only the {{ options.reset_link.title|t }} troubles me. Can't we avoid it using configuration translation?

I ran a git merge with this branch onto 2.0.x and didn't get any conflicts. Tested in a vanilla and Search API view, worked as expected.

Yes disregard #15.

Thanks you for your time on this. Setting as RTBC then, based on your feedback.

Some of those issues have been fixed in the 3.0.x-dev branch, could you give it a try?