Feat | Add OpenAPI documentation for OAuth2RocketChatSSOApiController v1

[matiasperrone-exo]

Task:

Ref: https://app.clickup.com/t/86b8e6k1y

[martinquiroga-exo]

LGTM

[caseylocker]

The RocketChatUserProfileSchema is created but never referenced from the endpoint's HTTP_OK response — the response uses a bare new OA\JsonContent() instead. An orphaned empty schema adds noise to the generated spec without providing value to API consumers.

Either wire it up by adding ref: '#/components/schemas/RocketChatUserProfile' to the JsonContent and marking the schema with additionalProperties: true (since the response proxies Rocket Chat's dynamic payload), or delete RocketChatUserProfileSchema.php entirely and keep the descriptive comment on the empty JsonContent.

[caseylocker]

See "red:" -> "ref:" comment.

For the empty rocket chat schema property just add a flag for additionalproperties so that it isn't empty. We don't control it but we don't want to just kick the can.

#[OA\Schema(
      schema: 'RocketChatUserProfile',
      type: 'object',
      additionalProperties: true,
      description: 'Rocket Chat SSO user profile. The response structure is the "data" portion of the Rocket Chat /api/v1/login endpoint response and is defined by the external Rocket Chat server.'
  )]

User's need to know that at least there are properties and they should refer to the docs for them.

[matiasperrone-exo]

Thanks @caseylocker for the comments. Now is ready to review again.
The typo "red" instead of "ref" and the suggested description were incorporated.