Improve search bar UX

[tristanlatr]

Search UX part 1: Result selection and shortcuts.

Search UX part 2: If the search box contains "docstring:" enable search in docstrings automatically.

Search UX part 3: Use a logical "and" in between search terms by default. Use leading '?' to make a term optional.

Add the « kind » field to the default index.

Do not give a boost to container type objects in the search index.

Show "Loading..." when the index file is not in memory yet

TODOs:

• Only load first 50 results by default and insert a button to load the entire list
• Do not store the "kind" field in the index at all, instead make it a "post-process field" that is applied after the query runs. That's probably not a good idea
• If a search yields no PUBLIC results at all, then display the private results automatically
• If a search yields no results AT ALL, then leverage the fuzzy search feature of lunrjs and re-launch the query with ~1
• Move/duplicate the "Show private" button inside the search box so easily accessible
• Load the query string from the URL parameter ?search=term
• If the search is launch from a submodule/one of the root modules of the system, propose to search only in the current module.

Fixes #822

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.38%. Comparing base (87ffe4c) to head (d1576fb).

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #934      +/-   ##
==========================================
- Coverage   93.38%   93.38%   -0.01%     
==========================================
  Files          48       48              
  Lines        8954     8949       -5     
  Branches     1640     1639       -1     
==========================================
- Hits         8362     8357       -5     
  Misses        336      336              
  Partials      256      256              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

According to pydoctor_primer, this change doesn't affect pydoctor warnings on a corpus of open source code. ✅

[github-actions]

According to pydoctor_primer, this change doesn't affect pydoctor warnings on a corpus of open source code. ✅

[github-actions]

According to pydoctor_primer, this change doesn't affect pydoctor warnings on a corpus of open source code. ✅

[github-actions]

According to pydoctor_primer, this change doesn't affect pydoctor warnings on a corpus of open source code. ✅

[github-actions]

According to pydoctor_primer, this change doesn't affect pydoctor warnings on a corpus of open source code. ✅

[github-actions]

According to pydoctor_primer, this change doesn't affect pydoctor warnings on a corpus of open source code. ✅

[github-actions]

According to pydoctor_primer, this change doesn't affect pydoctor warnings on a corpus of open source code. ✅

[github-actions]

According to pydoctor_primer, this change doesn't affect pydoctor warnings on a corpus of open source code. ✅

[github-actions]

According to pydoctor_primer, this change doesn't affect pydoctor warnings on a corpus of open source code. ✅

[github-actions]

According to pydoctor_primer, this change doesn't affect pydoctor warnings on a corpus of open source code. ✅

[github-actions]

According to pydoctor_primer, this change doesn't affect pydoctor warnings on a corpus of open source code. ✅