2024.3.0

Generated from the API spec of [Develocity API 2024.3][1].

\## What's Changed

ℹ️  This release is equivalent to the last alpha, 2024.3.0-alpha01 (new build of the same commit).

\### New API spec

- [Develocity API changelog][2]
- [Library API diff (see `library.api`)][3]

[1]: https://docs.gradle.com/enterprise/api-manual/#reference_documentation
[2]: https://docs.gradle.com/enterprise/api-manual/#2024_3
[3]: 2024.2.0...2024.3.0

\### Notable changes

- **Added**: many new API endpoints and features (see [API changelog][2])
- **Changed**: documentation improvements (library API)

**Full Changelog from 2024.2.0**: 2024.2.0...2024.3.0

**Full Changelog from 2024.3.0-alpha01**: 2024.3.0...2024.3.0-alpha01

Prepare for next release (#353)

Prepare for next release (#310)

Prepare for next release (#307)

Hide LoggerFactory from public API (#294)

Prepare for alpha release (#281)

Bump version for next release (#205)

Fix javadoc missing generated API (#200)

Move Dokka configuration to the `jvm-library` plugin, which is applied
before `test-suites`, and stop passing a fixed source root for Dokka so
that generated API source set is included. Also fix some configuration
avoidance smells.

When refactoring build logic into plugins, Dokka stopped recognizing the
correct source set. #199 fixed this by passing a specific source root to
Dokka, but this caused the resulting javadoc to not include the
generated API. Bisecting shows that moving the test suite setup
(456f769), making test suites be set up
before Dokka, was when the issue started.

Add missing APIs to GradleEnterpriseApi (#174)

The beta `ProjectsApi` (added in 2023.3) and `TestsApi` (added in
2023.4) weren't accessible from `GradleEnterpriseApi`. Fix and an
integration test to prevent it from happening again.

Fix builds paging when models param is used (#163)

Preserve the `models` param across `/api/builds` requests of
`getBuildsFlow`. Add more integration tests.

When the `models` param is used with `getBuildsFlow`, requests after the
first one (paging) don't send the `models` param, but they should. This
is the same issue faced with `query` (#134), due to this extension being
manually implemented. More integration test coverage should help.