Refactor the Search component to treat filter changes generically

The tests are all green which means functionally everything is working as expected.I have a done some basic restructuring for now (which might be silly) but i think it's a good start for now.I'll ask @phenaproxima to guide me more on this with what i need to follow in order to achieve the goal.

I will discuss this with @phenaproxima and update the status of the issue soon.

I think this is now ready and changes are inline with the discussion that i had with @phenaproxima.Marking it NR .

Tested manually and it seems that On selecting multiple categories, it does not announce the Count of selected categories when voiceover is on.

This generally looks good. I think we can remove filtersWrapper, it seems like a pointless extra layer around what $filters is already doing.

We do need to fix the announce problem that @narendrar found. I would suggest that we change the backend MultipleChoiceFilter class so that it accepts a "template string" that can be used for announcements, and then have the announce function in Svelte use that. Make it part of the filter's definition -- how does it want to announce a state change to the user? All the filters should be taking this sort of accessibility into account, but let's fix it for the MultipleChoiceFilter type first, and the other filter types later.

Re #9, This intermittent announce issue seems to exist on 2.0.x also and can be skipped for now.

This is making a ton of sense. There are a few more steps to go, but this is really solid so far!

I am facing issues in solving the test fails.I checked the URLs formed in both 2.0.x and this branch are same.

Turns out the tests were only failing because we weren't always passing the filters to load() in ProjectBrowser.svelte. That makes sense -- we probably always want to pass them explicitly.

I think with automated tests passing for a known reason, and the code changes being grokable, and me manual testing, I think this one looks good!

Automatically closed - issue fixed for 2 weeks with no activity.