Always build the docs

[tdcmeehan]

Description

There was a build failure on trunk because the docs failed to build. Docs only build currently if there's a change detected in the docs directory. However, there are some subtle interactions between the docs and the libraries and code that we use, so it's safest to always build the docs.

Motivation and Context

There was a build failure on trunk reported due to this issue (#25177).

Impact

Docs are relatively quick to build, so it should be safe to always build them.

Test Plan

CI

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

== NO RELEASE NOTE ==