Don't communicate the Filters button state by rotating the icon

apologies for the late reply am in the course of migrating and setting up a new computer so a few notifications slipped through. the link to the Drupal Design system is this one: https://www.figma.com/file/OqWgzAluHtsOd5uwm1lubFeH/💧-Drupal-Design-system?node-id=553%3A0 (the drop down button page could be found at the top the second from left - the section about states)

thank you for working on it! but it is odd. I successfully applied the patch to my drupal 9.5 install with project_browser dev even though the merge request shows a merge error. I've also checked the source afterwards that the rotation transform gets removed and the background-colour gets changed. so the changes got applied.
but somehow I've done two or three drush cr as well as cleared the caches in safari, firefox and edge but everything looks like no changes have been applied. therefor I am unable to confirm that everything is working as expected. ( I guess it might have to do with mutagen in my local environment - haven't had any problems with that on my old computer so far - will report back as soon as I figured out the root cause)

@libbna and others, one question. I think I figured out the possible issue why the changes haven't shown up on my end described in #16. is it possible that I have to manually trigger a svelte compile when reviewing patches for project browser? cuz I've noticed the changes in the search.svelte file are in place and get properly applied but in the browser they dont show up. looks like sveltejs/public/build/bundle.css doesn't reflect those yet. am not a developer and never worked with svelte on my own in the context of the issue queue therefor the probably basic question.

ahhhhhh thanks a lot @libbna! now I am able to see the changes after building.

about the changes now that I am able to see things in the browser. the icon doesn't rotate anymore and the color of the active state looks correct and good. thank you!

one detail about the iconography. for scanability I personally prefer to prepend the icon to the text that way a sighted user relying on a visual queue instead of reading is able to simply scan the icon and is able to skip the reading. But in the current state the user has to scan the text anyway first before reaching the icon. I've taken another look at the button anatomy in the drupal design system and my suggestion is in line with the guidelines there as well. meaning the icon is first and the text afterwards:

The only detail I am not sure if it is intended to have an icon for a none primary button?!

another detail is related to the following issue (https://www.drupal.org/project/project_browser/issues/3293909) we've discussed in yesterdays a11y office hour (see the talking point "mike - project browser patch" - the first of the two). Currently the icon has an alt attribute but it is missing a tooltip. Because the visible text for the button shows only "Filter" but it is basically the advanced filter and that could be reflected in the tooltip like it is already in the alt text. Only constraint and consensus in yesterdays meeting the text for the alt attribute and the tooltip shouldn't be identical. But guess if the other issue came to a final conclusion it could be adjusted to that?

I'll set the status back to needs work due to the icon position.