Kestra 2.0.0 introduces breaking changes to API error format and plugin defaults

The release of Kestra version 2.0.0, as detailed in the project's GitHub release notes, includes significant breaking changes that operators must address. The API error format has been updated to adopt RFC 9457 problem details, replacing the previous error response structure. Error responses no longer include fields such as `message`, `_links`, or `_embedded.errors[]`, and are now served as `application/problem+json` instead of `application/json`. Additionally, bulk endpoints now report per-item failures in `errors[]` rather than `invalids[]`. This change requires clients to branch on the `type` field and read the `detail` field for error information. Another notable breaking change involves the removal of the forced flag from flow-level `pluginDefaults`.

Operators should carefully review any integrations or custom tools that interact with Kestra's API, as the new error format may require updates to error-handling logic. Systems relying on the previous `pluginDefaults` behavior will also need to be adjusted to accommodate the removal of the forced flag. Testing these changes in a staging environment before deploying to production is strongly recommended to avoid disruptions. These updates reflect a broader trend in software projects adopting standardized formats like RFC 9457 for error handling, emphasizing interoperability and consistency across systems.