feat(search): Add react-freecodecamp-search to Nav

[Bouncey]

Pre-Submission Checklist

• Your pull request targets the staging branch of freeCodeCamp.
• Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
• You have only one commit (if not, squash them into one commit).
• All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

• Small bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would change existing functionality)
• Add new translation (feature adding new translations)

Checklist:

• Tested changes locally.
• Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #16166

Description

Search all the things!

[QuincyLarson]

@Bouncey OK - I just tested this locally. It looks great. I have some feedback for how it can be even more intuitive:

1. Drop the description and just show the title - this will be less overwhelming.
2. Suppress stubs from search results. Clicking through to a stub will be a negative user experience.
3. Group similar types of results. For example, Have a single header "Lesson" with the titles below it, then "Blog Articles" or "Guide Articles" or "Videos". Is it possible to highlight the matching part? Note that here I mistyped "trst", so it's highlighting "test" to show that this is how it's matching. This is subtle, but if it's possible, we should do something like this for usability purposes.
   
4. Make the text area completely white (#ffffff) instead of gray so it matches the rest of our UI elements
5. Add an magnifying glass symbol inside the search box (font awesome should have a good one) and color it Return Largest Numbers in Arrays - Not Recognizing Correct Answer #6400

[Bouncey]

So drop the description in favour of an extract that shows the match?

All styling and displaying of results in the dropdown is the responsibility of the freecodecamp/react-freecodecamp-search repo.

Suppressing stubs will be at the elasticsearch end of the process, freecodecamp/search

[QuincyLarson]

@Bouncey Yes - I think just showing say, the sentence that contains the match - would be fine. We can do this on the Search repo, but I think we can do these styling changes here on this PR first before we merge this.

[Bouncey]

Yes, I would need to update styles in the package, then update this PR with the next release

[QuincyLarson]

@Bouncey OK - I'm going to go ahead and merge this and we can open another PR to address it next.

[raisedadead]

@QuincyLarson @Bouncey Was this reverted? If so, was it handled by something else? In either case the linked issue should have been either re-opened or any other PR which handled this should have been linked.

[Bouncey]

@raisedadead I don't understand what you mean? I'm not aware of this being reverted.

[raisedadead]

See 8485041