[feat] <Navigation> Standardize search input for navigation and allow for an optional exposed search bar

[jknilans]

Description

The initial ask for this issue is to enable a future version of the shared navigation component to allow for an exposed search on websites that heavily rely on search. The initial use case is for the Red Hat Ecosystem Catalog, which search is the primary use case for customers.

In working through this for the Ecosystem Catalog, @dcaryll mentioned that it would be useful to explore if we could standardize components and usage for any website that uses the new navigation, regardless if they choose to expose the search by default or if it requires clicking on a search icon. In looking through the many instances of search among different Red Hat websites, I noticed, as you're probably aware, that there is a lack of consistency in how we display the search bar once a user has clicked on the magnifying glass icon. The following solution suggests a way to standardize this experience using already-existing components in PatternFly4.

Suggested solution

Here's a Sketch wireframe showing the expected behavior for websites that choose to adopt the new navigation option.

If the wireframe doesn't load immediately, it helps to copy the URL and paste it in a new tab. For some reason Sketch cloud sometimes has a hiccup when clicking directly on the link.

The solution would provide consistency across websites, ensure that search bars have multiple states, and hopefully reduce developer work across teams.

Example API

No response

Additional context

[dcaryll]

cc @coreyvickery @markcaron @marionnegp

[bennypowers]

https://github.com/orgs/RedHat-UX/discussions/1624
#868
#375
#310