Manually refresh Quarto docs & revert workflow experiment

[nrichers]

Pull Request Description

What and why?

With our Quarto workflows currently blocked by new branch protection rules, this PR:

• Reverts the changes from Update API host URL to prod in reference #433 for quarto-docs.yaml
• Includes the generated QMD files for the Python API

How to test

What needs special review?

Dependencies, breaking changes, and deployment notes

Release notes

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

PR Summary

This pull request introduces extensive documentation enhancements across multiple Quarto (QMD) files related to test suite execution, model validation, prompt validation, and statsmodels integrations. The primary changes include:

• The addition of return type annotations to a large number of function signatures for enhanced clarity and support of static type checking. For example, functions in the areas of regression metrics, classification evaluation, clustering metrics, and NLP scorers have been updated.

• Minor formatting updates have been applied in documentation strings to standardize list notation (e.g., using standard list brackets rather than escaped markdown).

• Updates in docstring documentation for methods such as assign_predictions and new helper methods like set_metric have been added or refined.

These changes aim to improve the overall readability, maintainability, and consistency of the codebase documentation, ensuring that both the technical and descriptive aspects of the test suite and evaluation modules remain clear to developers and users.

Test Suggestions

• Run the entire test suite to ensure that the newly added type annotations do not affect runtime behavior.
• Use static analysis tools (e.g., mypy, pylint) to verify that all type hints are correctly formatted and that they integrate smoothly with the codebase.
• Render the Quarto documentation to confirm that formatting—including any new list notations and docstrings—appears as expected.
• Compare outputs from functions before and after the change to ensure that adding return type annotations has not inadvertently altered any logic.

[validbeck]

🤞🏻