Make existing filter warnings and search states more actionable

[FennexFox]

Problem

Feedback suggests that some users miss expected drives or do not immediately understand why a drive is hidden.

The app already displays warnings when filters hide drives, so this issue should not be treated as "add a missing warning from scratch."

Instead, the issue is that the existing filter/search state needs to be more actionable and easier to notice during first-time use.

This is especially important after renaming TWR to Acceleration, because users may be filtering by a stat they know from the game but still not understand why familiar early drives disappear.

Goal

Improve the UX around hidden drives, active filters, and search results.

Users should be able to answer these questions immediately:

• Are drives hidden by current filters?
• Which filter is hiding the drive I expected?
• How do I reset or relax that filter?
• If I searched for a specific drive, why is it still not visible or why is it shown as filtered?

Scope

This issue improves the presentation and actionability of existing filter warnings and search/filter interactions.

It is not primarily about implementing the warning system itself, since warnings already exist.

Suggested direction

Make filter warnings more contextual and action-oriented.

Examples:

42 drives are hidden by current filters.
[Reset filters] [Show hidden drives]

For a searched drive:

Burner is hidden by the current minimum acceleration filter.
[Show anyway] [Reset acceleration filter]

If searched drives are shown despite failing filters:

Burner is shown because it matches your search.
It does not meet the current minimum acceleration filter.

The exact design can vary, but the user should not have to infer the cause from filter controls alone.

Acceptance criteria

• Existing hidden-drive warnings are reviewed for visibility, placement, and wording.
• Warnings identify the relevant filter where practical, especially acceleration/TWR-related filters.
• Warnings provide a direct action such as reset filter, relax filter, or show hidden results.
• Search behavior is explicit when a matching drive is hidden by active filters.
• If a searched drive is shown despite failing filters, the UI marks that state clearly.
• The UI avoids making search feel broken when filters are the reason for missing results.
• The terminology is aligned with the Acceleration wording from the related terminology issue.
• Existing filter logic continues to work unless deliberately adjusted.

Non-goals

• Do not add a brand-new warning system if the existing one can be improved.
• Do not implement campaign save parsing.
• Do not redesign the full filter panel in this issue unless needed for the warning/action flow.