Fix documentation lookup

[mcbarton]

Closes #456

The reason you couldn't look up some of these pieces of documentation in cppreference was due to 2 issues. One is that you need to look up something according to its name in the tag file (e.g. you search for sort and not std::sort). This requires no changes to xeus-cpp. The other issue with documentation lookup, is that it only currently looks for something equal to whatever was after the ? and ignores anything after a space occurs. e.g. ?move, ?move (utility) and ?move (algorithm) will look up the same thing in the cppreference tagfile (i.e move). Once I knew the second bug, I worked with chatgpt, and found the following one line diff to fix the documentation issue. Images below are just to show it working.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.28%. Comparing base (b72097a) to head (53d9e2d).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #460   +/-   ##
=======================================
  Coverage   80.28%   80.28%           
=======================================
  Files          21       21           
  Lines         847      847           
  Branches       78       78           
=======================================
  Hits          680      680           
  Misses        167      167           

Files with missing lines	Coverage Δ
src/xinspect.cpp	91.89% <100.00%> (ø)

Files with missing lines	Coverage Δ
src/xinspect.cpp	91.89% <100.00%> (ø)

🚀 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]

clang-tidy review says "All clean, LGTM! 👍"

[JohanMabille]

Thanks for the fix! Can you add a test after this one to check that the interpreter correctly finds the documentation for move (utility) for instance?

Also what does happen if someone wrongy types ?std::vector push_back ?

[mcbarton]

?std::vector push_back ?

@JohanMabille thanks for the review. I'll look into writing a test tomorrow, and ping you when its ready.

I'm not sure what is wanted if someone executes ?std::vector push_back ?, but on xeus-cpps current main and this PR you get the documentation for std::vector. What would you expect/want to happen?

[mcbarton]

Added 2 tests fetch_documentation_move_algorithm and fetch_documentation_move_utility. This checks we can differentiate between the 2.

I feel someone executing ?std::vector push_back ? is a different issue, and you currently get with this PR the same as what you get on main.

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[JohanMabille]

What would you expect/want to happen?

Since this PR allows to parse what comes after a space, I was wondering if we would get an error, or if there was an additional matching pattern for finding the tag.

[JohanMabille]

Ok let's get this one in!