UI: Key / Value search is stuck on subsequent screens

#### Overview of the Issue

In the key / value search, when you search for a term then click on found key the search is stuck on the next screen.

#### Reproduction Steps

Steps to reproduce this issue, eg:

1. Browse to Key/Value
2. Search for a Key
3. Click on Key
4. Observe the Search is still filtering on the previous search

### Consul info for both Client and Server

Client info

```
agent:
check_monitors = 0
check_ttls = 0
checks = 1
services = 1
build:
prerelease =
revision = 2308c75e
version = 1.12.3
version_metadata =
consul:
acl = enabled
known_servers = 3
server = false
runtime:
arch = amd64
cpu_count = 2
goroutines = 76
max_procs = 2
os = linux
version = go1.18.1
serf_lan:
coordinate_resets = 0
encrypted = true
event_queue = 0
event_time = 11173
failed = 1
health_score = 0
intent_queue = 0
left = 0
member_time = 135306
members = 314
query_queue = 0
query_time = 15
```

Server info

```
agent:
check_monitors = 1
check_ttls = 0
checks = 2
services = 2
build:
prerelease =
revision = 2308c75e
version = 1.12.3
version_metadata =
consul:
acl = enabled
bootstrap = false
known_datacenters = 3
leader = false
leader_addr = ...
server = true
raft:
applied_index = 228784916
commit_index = 228784916
fsm_pending = 0
last_contact = 26.026247ms
last_log_index = 228784916
last_log_term = 2414
last_snapshot_index = 228774823
last_snapshot_term = 2414
latest_configuration = ...
latest_configuration_index = 0
num_peers = 2
protocol_version = 3
protocol_version_max = 3
protocol_version_min = 0
snapshot_version_max = 1
snapshot_version_min = 0
state = Follower
term = 2414
runtime:
arch = amd64
cpu_count = 4
goroutines = 1295
max_procs = 4
os = linux
version = go1.18.1
serf_lan:
coordinate_resets = 0
encrypted = true
event_queue = 0
event_time = 11173
failed = 1
health_score = 0
intent_queue = 0
left = 0
member_time = 135306
members = 314
query_queue = 0
query_time = 15
serf_wan:
coordinate_resets = 0
encrypted = true
event_queue = 0
event_time = 1
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 6421
members = 9
query_queue = 0
query_time = 1
```

### Operating system and Environment details

Client and Server on 1.12.3. Have another cluster with enterprise with the same issue.

Start by reproducing the Key/Value search flow described in the issue: search for a key, select a result, and inspect the subsequent screen. Trace the UI state that carries the previous search between these screens; done means navigating to the selected key no longer keeps filtering by the earlier search term, including on Consul 1.12.3 behavior.

Written by the indexing model from the issue text.