Centralize default HTTP timeouts across session, compatibility, and upload flows

[Copilot]

This picks up a small roadmap reliability task by replacing scattered hardcoded HTTP timeouts with a shared configuration surface. The goal is to make timeout behavior consistent across session bootstrap, compatibility detection, scraping fallbacks, and upload paths.

• Add shared timeout defaults

  • Introduce src/py_moodle/config.py with named timeout policies for:
    • routine requests
    • short-lived scrape/probe requests
    • standard uploads
    • large package uploads

• Replace hardcoded values in core flows

  • session.py: use the shared request timeout for sesskey fallback fetches and webservice calls
  • compat.py: use the shared request timeout for version detection via webservice and dashboard probing
  • module.py: use the shared scrape timeout for label intro fallback scraping
  • upload.py: default webservice uploads to the shared upload timeout
  • draftfile.py: default draft uploads to the shared large-upload timeout and add explicit request timeouts to draft-item and repo-detection calls
  • scorm.py: reuse the shared large-upload timeout for SCORM package uploads

• Add focused regression coverage

  • Add unit tests to verify the updated code paths consume the centralized timeout constants rather than embedding local values

Example of the new timeout contract:

from py_moodle.config import (
    DEFAULT_REQUEST_TIMEOUT,
    DEFAULT_SCRAPE_TIMEOUT,
    DEFAULT_UPLOAD_TIMEOUT,
    DEFAULT_LARGE_UPLOAD_TIMEOUT,
)

response = session.post(url, timeout=DEFAULT_REQUEST_TIMEOUT)
itemid = upload_file_webservice(base_url, token, file_path, DEFAULT_UPLOAD_TIMEOUT)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.