fix(rst): ensure blank line before bullet lists

[moon-jam]

Why

Notice that #58748 fixed a bullet points rendering issue caused by missing blank lines before *, but some files still have the same problem. This PR adds a fix for them.

For example:

How

I used a simple script below to check that bullet points render properly and fixed them manually.

Script to find bullet points format error

from pathlib import Path


def is_bullet_line(line: str) -> bool:
    return line.startswith("* ")


def is_blank(line: str) -> bool:
    return line.strip() == ""


def main():
    for rst in Path(".").rglob("*.rst"):
        lines = rst.read_text(encoding="utf-8").splitlines()

        for i, line in enumerate(lines):
            if not is_bullet_line(line):
                continue

            if i == 0:
                continue

            prev = lines[i - 1]

            if is_blank(prev):
                continue
            if (
                prev.startswith("*")
                or prev.startswith(" ")
                or prev.startswith("=")
                or prev.startswith("''")
                or prev.startswith("~")
                or prev.startswith("-")
            ):
                continue

            print(f"{rst}:{i + 1}: " f'bullet "*" should be preceded by a blank line')


if __name__ == "__main__":
    main()

Optional / Future

• Maybe I could integrate a rst linter in pre-commit hook later.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[github-actions]

Backport failed to create: v3-1-test. View the failure log Run details

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker fe80fed v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue