WIP: Add docs in search

[gagdiez]

This PR adds the ability to search for docs directly on the general searchbar

We might want to discuss:

• Removing the "All" tab
• Changing the "Apps" tab, so the result comes from NEAR Catalog instead of showing only components

[shelegdmitriy]

Overall looks good! Thank you @matiasbenary for contribution! But I want to highlight that all this changes should be added to src/Search/IndexPage.jsx page also.

Removing the "All" tab

Well, I think we can remove this tab from TypeAheadDropdown but let's leave it on src/Search/IndexPage.jsx. There is enough space for that there. WDYT?

Changing the "Apps" tab, so the result comes from NEAR Catalog instead of showing only components

Apps tab already has the nearcatalog records if I'm not mistaken 🤔

Also, I do understand that this PR is in progress but I think this UI could be improved a bit:

1. Let's display a doc's category instead of COMPONENTS 2389 (or Docs after changes). Seems like we do have such data so why don't we use it?
2. Let's add a hover effect like text-decoration: underline for title or something

[shelegdmitriy]

Suggested change

	case "Docs":
	return state.components.hits?.length > 0 ? (
	<DisplayResultsByFacet title="Components" count={state.docs.hitsTotal} items={topmostComponents(false)} />
	) : (
	<>
	<TextMessage message={`No Component matches were found for "${state.term}".`} />
	<TextMessage
	message={`Trying to find a app built by an user? Try search their account id.`}
	$fontSize="12px"
	$top="45%"
	/>{" "}
	</>
	);
	case "Docs":
	return state.docs.hits?.length > 0 ? (
	<DisplayResultsByFacet title="Docs" count={state.docs.hitsTotal} items={state.docs.hits} />
	) : (
	<>
	<TextMessage message={`No matches were found for "${state.term}".`} />
	</>
	);

[shelegdmitriy]

Suggested change

	// Return the count for Apps
	// Return the count for Docs

[shelegdmitriy]

Suggested change

	if (state.selectedTab === "Docs") {
	return <Items>{state.docs.hits}</Items>;
	}

Let's remove this changes and apply my next suggestion instead

[shelegdmitriy]

Hey @matiasbenary and @gagdiez! Seems like there is no need in this PR in favour of this near/near-discovery#1249 right?

[gagdiez]

@shelegdmitriy indeed, closing this one