fix(tests): mock PromptSession to prevent console error

[Pouyanpi]

Description

The tests in tests/test_cli.py and tests/test_cli_migration.py were failing with the following error:

prompt_toolkit.output.win32.NoConsoleScreenBufferError: Found xterm-256color, while expecting a Windows console. Maybe try to run this program using "winpty" or run it in cmd.exe instead. Or otherwise, in case of Cygwin, use the Python executable that is compiled for Cygwin.

This error occurs because the prompt_toolkit library expects a Windows console but find xterm-256color instead. This happens when running tests in an environment that doesn't have a proper console buffer. This issue occurs in Windows GitHub runners when the runner is windows-latest.

Root Cause

The PromptSession class from the prompt_toolkit library attempts to create a console application, which fails in environments without a proper console buffer, leading to the NoConsoleScreenBufferError.

Fix

To resolve this issue, the PromptSession class is mocked during the tests to avoid initialization. This prevents the NoConsoleScreenBufferError from occurring.

Testing

• Verified that the tests in tests/test_cli.py and tests/test_cli_migration.py pass successfully in both local and CI.
• Ensured that the mocking does not interfere with the actual functionality being tested.

Related Issue(s)

prompt-toolkit/python-prompt-toolkit#406

Checklist

• I've read the CONTRIBUTING guidelines.
• I've updated the documentation if applicable.
• I've added tests if applicable.
• @mentions of the person or team responsible for reviewing proposed changes.

[schuellc-nvidia]

Thank you for fixing this! Looks good!