[Asgardeo Docs] Remove behavioral change notice for omitting null fields in DCR API response

[BimsaraBodaragama]

Purpose

Remove the temporary public notice added in the OAuth2 Dynamic Client Registration (DCR) API documentation [1] after the grace period has ended.
The note previously informed users about the upcoming behavioral change to omit null fields from the DCR API response [2] in alignment with REST best practices.

Goals

• Remove the temporary grace-period notice from the DCR API documentation.
• Align with the old documentation [1] (before the change notice was added via [3] [4]) with no notice in API docs.

Approach

• Removed the yellow-highlighted HTML note block under the info.description section of oauth-dcr.yaml.

NOTE:
The grace period for returning null fields ended on May 1, 2026.
With this update, the notice about the grace period on the documentation will be removed after May 1, 2026.
In parallel, the behaviour of the DCR response should be changed to omit null fields in the response as well [5] [6].

---

Related Issues

• https://github.com/wso2-enterprise/asgardeo-product/issues/33412

---

• [1] https://wso2.com/asgardeo/docs/apis/dynamic-client-registration-rest-api/
• [2] Mail: Handling Null Fields in DCR API Response
• [3] https://github.com/wso2-enterprise/asgardeo-product/issues/33411
• [4] [Asgardeo Docs] Add behavioral change notice for omitting null fields in DCR API response #5651
• [5] https://github.com/wso2-enterprise/asgardeo-product/issues/33413
• [6] https://github.com/wso2-enterprise/asgardeo-deployment-helm-is/pull/1360

[BimsaraBodaragama]

✅ Fix Verification

The update was verified locally in both dark and light modes of the Asgardeo Docs site to ensure consistent rendering and readability.

Dark Mode Preview

Light Mode Preview

[BimsaraBodaragama]

⚠️ Important Notice

This PR should be merged after the grace period ends on May 1, 2026.