Add most recent dbt-docs changes

[FishtownBuildBot]

Auto generated changes from generate-docs-for-dbt-core.yml workflow

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 88.71%. Comparing base (d4a6482) to head (be45638).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #10307 +/- ## ========================================== - Coverage 88.74% 88.71% -0.04% ========================================== Files 180 180 Lines 22483 22483 ========================================== - Hits 19953 19946 -7 - Misses 2530 2537 +7 ``` | [Flag](https://app.codecov.io/gh/dbt-labs/dbt-core/pull/10307/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=dbt-labs) | Coverage Δ | | |---|---|---| | [integration](https://app.codecov.io/gh/dbt-labs/dbt-core/pull/10307/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=dbt-labs) | `85.97% <ø> (-0.10%)` | :arrow_down: | | [unit](https://app.codecov.io/gh/dbt-labs/dbt-core/pull/10307/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=dbt-labs) | `61.78% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=dbt-labs#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[MichelleArk]

Sanity checking - these changes are covered by the 🎩 done in https://github.com/dbt-labs/dbt-docs/pull/513, right @aranke ?

[aranke]

Sanity checking - these changes are covered by the 🎩 done in https://github.com/dbt-labs/dbt-docs/pull/513, right @aranke?

Yes, correct. I technically ran this workflow off https://github.com/dbt-labs/dbt-docs/pull/514, but is identical to changes from https://github.com/dbt-labs/dbt-docs/pull/513

[github-actions[bot]]

The backport to 1.7.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.7.latest 1.7.latest
# Navigate to the new working tree
cd .worktrees/backport-1.7.latest
# Create a new branch
git switch --create backport-10307-to-1.7.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8ee8b2560a1ff05f2451855cc6c9c93aa6388309
# Push it to GitHub
git push --set-upstream origin backport-10307-to-1.7.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.7.latest

Then, create a pull request where the base branch is 1.7.latest and the compare/head branch is backport-10307-to-1.7.latest.

[github-actions[bot]]

The backport to 1.6.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.6.latest 1.6.latest
# Navigate to the new working tree
cd .worktrees/backport-1.6.latest
# Create a new branch
git switch --create backport-10307-to-1.6.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8ee8b2560a1ff05f2451855cc6c9c93aa6388309
# Push it to GitHub
git push --set-upstream origin backport-10307-to-1.6.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.6.latest

Then, create a pull request where the base branch is 1.6.latest and the compare/head branch is backport-10307-to-1.6.latest.