[VAULT-34704] UI: update FilterInput component to use Hds::Form::TextInput

[didoo]

Description

What does this PR do?

• replaces the internal implementation of FilterInput with the equivalent Hds::Form::TextInput::Base
  • in the process we have made a few structural changes:
    • removed the <div class="control > wrapper (not needed anymore)
    • removed the autofocus feature (has negative accessibility implications, see thread)
• updated all the existing FilterInput instances to use the correct Hds::Form::TextInput::Base arguments/API
• updated the integration tests for the FilterInput component

Jira ticket: https://hashicorp.atlassian.net/browse/VAULT-34704

A few video recordings of the updates UIs:

• https://github.com/user-attachments/assets/1415e3ae-ecfd-4747-9471-9bab0a951adf
• https://github.com/user-attachments/assets/0782dbcb-c118-43a2-b62c-a365dda16482
• https://github.com/user-attachments/assets/332f4045-3444-4886-8420-5a878bacdfc7
• https://github.com/user-attachments/assets/041c337b-edbb-485b-a3aa-0068e58364f7

TODO only if you're a HashiCorp employee

• Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
  • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
• ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
  of a public function, even if that change is in a CE file, double check that
  applying the patch for this PR to the ENT repo and running tests doesn't
  break any tests. Sometimes ENT only tests rely on public functions in CE
  files.
• Jira: If this change has an associated Jira, it's referenced either
  in the PR description, commit message, or branch name.
• RFC: If this change has an associated RFC, please link it in the description.
• ENT PR: If this change has an associated ENT PR, please link it in the
  description. Also, make sure the changelog is in this PR, not in your ENT PR.

[github-actions]

CI Results:
All Go tests succeeded! ✅

[github-actions]

Build Results:
All builds succeeded! ✅

[hellobontempo]

I don't want to blow out the scope of this PR but it seems like this can be removed (and here) since the input self-generates an id

[hellobontempo]

Looks good! Just some non-blocking questions, I'm mostly wondering if we can do some additional cleanup and remove redundant @id args.

[didoo]

Looks good! Just some non-blocking questions, I'm mostly wondering if we can do some additional cleanup and remove redundant @id args.

@hellobontempo I am worried that removing @ids without knowing if they're used in other parts of the codebase could break something. And checking if they are used or not may not be trivial (for me at least). So I prefer to keep the "logic" as is, unless it's clear that something is not used/needed anymore.

@Monkeychip maybe you can collect these cases in your follow-up cleanup epic?

[hellobontempo]

Looks good! Just some non-blocking questions, I'm mostly wondering if we can do some additional cleanup and remove redundant @id args.

@hellobontempo I am worried that removing @ids without knowing if they're used in other parts of the codebase could break something. And checking if they are used or not may not be trivial (for me at least). So I prefer to keep the "logic" as is, unless it's clear that something is not used/needed anymore.

@Monkeychip maybe you can collect these cases in your follow-up cleanup epic?

☝️ ➕ ➕ That sounds good to me! It's fairly clear to me that it's not needed anymore, but I agree it makes the most sense to tackle as follow-on cleanup. This form component swap is a lot as it is and keeping the scope narrow is important.