add pagination cap warning and improve first-run experience

[dvoraj75]

This pull request implements two main improvements: it adds a warning when the poller hits the pagination cap and improves the first-run experience by handling config errors with user-friendly messages and clean exits. Logging is now initialised before config loading to ensure all errors are formatted and actionable. Corresponding documentation and tests have been updated to reflect these changes.

User experience improvements:

• The CLI now catches ConfigError during startup and logs clear, actionable messages: if the config file is missing, the user is prompted to run forgewatch setup; if invalid, the user is told to check the config file. In both cases, the daemon exits cleanly with code 1. Logging is initialised before config loading to ensure all errors are properly formatted. [1] [2] [3] [4]

Pagination and poller enhancements:

• The poller now logs a warning if the pagination cap (_MAX_PAGES) is reached and more results are available, suggesting the user narrow their repo filter. [1] [2] [3]

Testing improvements:

• Added tests to verify that config errors result in clean exits with appropriate hints, and that the pagination cap warning is logged only when appropriate. [1] [2]

Documentation and versioning:

• Updated documentation to describe the new error handling and pagination warning behaviors. [1] [2] [3] [4]
• Bumped version to 1.5.0.dev and updated the changelog. [1] [2]

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
1712	1669	97%	90%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
forgewatch/_main_.py	98%	🟢
forgewatch/poller.py	96%	🟢
TOTAL	97%	🟢

updated for commit: fd3a80b by action🐍