Add create_result and update_order

[diazruy]

• Now using output directly as generated from OpenAPI generator, with no modifications. This nukes previous manual edits performed to various parts which were dangerous and easy to overlook (most of which were technically unnecessary and have been dealt with in different manners (for example, see this). No further manual modifications should be being made to the generated files to prevent this.
• scripts/generate_clients.sh in connect has been replaced by individual rake tasks per language and the Ruby one has been made to consume a version number (e.g. rake connect_client:ruby[1.0.0]) that gets piped into the generated client, as well as copying the updated files to the sibling folder containing the gem, ready for publishing.
• Now includes the models generated off of the Swagger schemas, given that the responses to client calls (which now have explicit schemas for better documentation) would otherwise be wrapped in InlineResponse200X classes which makes for a poor dev UX when using the client. Now the responses are more clearly PrimaryConnectClient::Orders, PrimaryConnectClient::OrderIds, etc.
• Adds the new update_order and the previously undocumented create_result API endpoints

[shawnd]

Check if manual edits here need to be carried over:
https://github.com/PrimaryDotHealth/connect-ruby-client/pull/11/files?diff=split&w=0#diff-b97af097a57a828723b654c6e2769dab866159b5d2ddce9ed1b46fc9b881334eL145-L198

[DamonGroove]

lgtm

[diazruy]

@shawnd

Check if manual edits here need to be carried over: #11 (files)

So I followed the rabbit hole, and turns out that OpenAPI doesn't have a "good" way to handle redirect responses. The only suggestion I found was this one, which suggests indicating that the response has a Location header, which I did by adding

      response(302, 'found') do
        header 'Location', schema:  { type: :string }, description: 'The signed URL to download the report'

which correctly adds the documentation like this

IMPORTANT: rswag docs indicate that the header should be specified like

        header 'Location', type: :string, description: 'The signed URL to download the report'

(without the schema:), but this actually causes OpenAPI generator to choke on it given that the generated YML ends up like

      responses:
        '302':
          description: found
          headers:
            location:
              type: string
              description: The signed URL to download the report

instead of

      responses:
        '302':
          description: found
          headers:
            location:
-              schema:
-                type: string
+              type: string
              description: The signed URL to download the report

which is actually what the Swagger docs indicate it should be.

That all said, even with these changes, the generated get_lab_report method on the client still returns nil, which is what I think @samsohn28 was trying to get around. I think what needs to happen is that when we want access to the response headers, we need to call get_lab_report_with_http_info instead of get_lab_report (which uses get_lab_report_with_http_info internally and returns the data exclusively), which returns not just the data (which is useless in our case) but also the status_code, and (more importantly) the headers, which can then be used to follow the redirect.

Interestingly enough, looks like health is not even actually yet using the get_lab_report endpoint anyway.

[samsohn28]

Awesome, thanks for handling the manual edits I made!