gh-140870: PyREPL auto-complete module attributes in import statements

[loic-simon]

Add the ability for _pyrepl._module_completer.ModuleCompleter to suggest attributes, in addition to modules.

If the module to import from is not imported yet, ask the user if they want to import it.
This is done by adding the notion of completion action to _pyrepl.completing_reader.CompletingReader:

• get_completions can return a completion action, in addtion to the suggestions list
• A completion action is a prompt to show + a callback to call if the user press TAB again
• The callback can return a message to show instead (here, if import failed)
• After the callback is fired, get_completions is called again, so it can propose new results (here, module attributes)
• If the user does any other input than TAB when the prompt is shown, the action is discarded

Other changes:

• I had to tweak a little the code used to display a message below the prompt, to handle the case when it doesn't fit on the console
• Some unrelated tests to get the coverage rate of _module_completer to 100% (in a separate commit, I can remove it if needed)

Interactive WebAssembly demo (up to date): https://pyrepl-attributes-import-completion.pages.dev

Possible improvement (probably in a follow-up PR): make modules printing stuff when imported not mess with the prompt ; see this Discourse message

• Issue: PyREPL: auto-complete module attributes in import statements #140870

[tomasr8]

Some unrelated tests to get the coverage rate of _module_completer to 100% (in a separate commit, I can remove it if needed)

Could you extract those into a separate PR? I think those are nice to have in any case and we can merge it quickly :)

[loic-simon]

Could you extract those into a separate PR? I think those are nice to have in any case and we can merge it quickly :)

Sure, #143244

[tomasr8]

Quick initial question, can we disable the prompt for stdlib modules? I don't think there should be any concerns with auto-importing from the stdlib

[loic-simon]

We could, yes. I don't think we can decide to auto-import solely on module name (to take care of potential shadowing by first/third-party modules), so we would need to look the module spec location, but since we already have self._is_stdlib_module and self._global_cache that should be easy and fast!

(I'll won't be to get my hands on the code until early January tho)