VACMS-18805: Configurations for updating KB search.

[JakeBapple]

Description

This work updates the configurations for the knowledge base search functionality.

Closes #18805.

Testing done

Local search testing with A/B results for different scenarios outlined in ticket #8136

QA steps

What needs to be checked to prove this works?
Search within the knowledge base for something you need.
What needs to be checked to prove it didn't break any related things?
Perform basic searches in knowledge base to make sure it is behaving as expected.
What variations of circumstances (users, actions, values) need to be checked?
Add in some of the stopwords located here to see if they populate the search results (they shouldn't).

Definition of Done

• Documentation has been updated, if applicable.
• Tests have been added if necessary.
• Automated tests have passed.
• Code Quality Tests have passed.
• Acceptance Criteria in related issue are met.
• Manual Code Review Approved.
• If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing

Is this PR blocked by another PR?

• DO NOT MERGE

Does this PR need review from a Product Owner

• Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

• Yes, and it's written in issue ____ and queued for publication.
  • Merge and ping the UX writer so they are ready to publish after deployment
• Yes, but it hasn't yet been written
  • Don't merge yet -- ping the UX writer to write and queue content
• No announcement is needed for this code change.
  • Merge & carry on unburdened by announcements

[edmund-dunn]

Nice work! This all looks good!