Show files filter status

[stefanhaller]

• PR Description

This PR contains three improvements to the Files panel filtering:

• it allows the user to switch to a different filter type (or reset the filter) when we are auto-showing only conflicting files
• it shows the filter menu as radio buttons
• it displays the current filter in the top-right corner of the Files panel's frame

See the individual commits for details.

• Please check if the PR fulfills these requirements

• Cheatsheets are up-to-date (run go generate ./...)
• Code has been formatted (see here)
• Tests have been added/updated (see here for the integration test guide)
• Text is internationalised (see here)
• If a new UserConfig entry was added, make sure it can be hot-reloaded (see here)
• Docs have been updated if necessary
• You've read through your own file changes for silly mistakes etc

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for a1838d31	✅ 75.86%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (a1838d3)	Report Missing	Report Missing	Report Missing
Head commit (aad2622)	52556	45513	86.60%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#4230)	29	22	75.86%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

[jesseduffield]

LGTM: tested and it works well

[stefanhaller]

@jesseduffield Thanks. I can only merge this after #4226 is merged though, because it depends on it (and sits on top of it).