[openapi] Schema is not added when a record from other module is used

[abeykoon]

Description:

Consider the following resource function in a service

    resource function post resources/services/[string serviceId]/
            connection\-schemas(http:RequestContext ctx,
            @http:Payload api:ConnectionSchemaInfo[] connectionSchema) returns http:Created
            |http:InternalServerError|http:NotFound|http:BadRequest {

Here

1. payload is a ConnectionSchemaInfo[]
2. ConnectionSchemaInfo coming from a different module (api) w.r.t where service.bal is.

When OpenAPI definition is generated, schema related to this payload is not generated. When record definition was moved to same module, it was generated successfully.

Steps to reproduce:

Please see above

Affected Versions:

Ballerina 2201.7.1

OS, DB, other environment details and versions:

Related Issues (optional):
https://github.com/wso2-enterprise/choreo/issues/23781

[TharmiganK]

The above PR will fix the request body generation for the above mentioned scenario.

While fixing this issue, I saw some gap between the allowed payload types in the http module and the generated request body schema. These inconsistencies will be addressed in a separate issue.