Vim keybindings conflict with text input in component filter

### Describe the Bug

When typing in the component filter input, vim-style navigation keys (h, j, k, l) are intercepted as navigation shortcuts instead of being treated as text input.

### Expected Behavior

When a filter input is active/focused, all keypresses should be captured by the text input and not passed through to navigation handlers.

### Steps to Reproduce

- Open atmos TUI
- Navigate to the component list
- Start filtering (e.g. type `graphql`)
- Observe that `h` triggers a left-panel navigation instead of appending to the filter string

### Screenshots

_No response_

### Environment

`Atmos 1.207.0 on darwin/arm64`

### Additional Context

_No response_

Reproduce the issue in the Atmos TUI by opening the component list, focusing its filter, and typing `graphql`. Trace the filter input and Vim-style navigation key handlers; done means focused filter input treats h, j, k, and l as text and does not trigger panel navigation.

Written by the indexing model from the issue text.