Centralize input handling through UserInterface for future pygame UI support

[Copilot]

Problem

When using the game, users had to switch between the console and UI to provide input in certain situations (bank deposits/withdrawals, tavern betting, stats viewing). This created a poor user experience and prevented the future implementation of a pygame-based UI, as direct input() calls were scattered throughout the location code.

Solution

This PR centralizes all user input handling through the UserInterface class by:

1. Adding a new getInput() method to the UserInterface class that handles all text/numeric input consistently
2. Replacing all direct input() calls in location code with calls to userInterface.getInput()
3. Simplifying code by removing redundant UI formatting calls (now handled centrally)

Changes

Core Changes

• src/ui/userInterface.py: Added getInput(prompt) method to centralize input handling
• src/location/bank.py: Updated deposit() and withdraw() to use userInterface.getInput()
• src/location/tavern.py: Updated changeBet() to use userInterface.getInput()
• src/location/home.py: Updated displayStats() to use userInterface.getInput()

Test Updates

• Updated all related tests to mock the new getInput() method
• Added comprehensive test coverage for the new functionality
• All 67 tests pass

Benefits

✅ No more context switching - All input now flows through a single interface
✅ Future-ready - Pygame UI can be implemented by simply overriding UserInterface methods
✅ Cleaner code - Reduced duplication and improved separation of concerns
✅ Fully tested - Comprehensive test coverage with no regressions

Example

Before:

# Direct console input scattered in location code
amount = float(input("> "))

After:

# Centralized through UserInterface
userInput = self.userInterface.getInput(self.currentPrompt.text)
amount = float(userInput)

This architectural improvement makes it straightforward to swap in alternative UI implementations (pygame, web UI, etc.) in the future without modifying any location-specific code.

Fixes #[issue_number]

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Support all needed input through pygame UI</issue_title>
<issue_description>When using the pygame UI, the user has to switch back to the console to provide input sometimes. All input should be capable of being handled by the pygame UI so the user doesn't have to context switch.</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes #42

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.