Implement Autocomplete of OAS3 with 3scale account data

[damianpm]

What this PR does / why we need it:

Implements autocomplete of OAS 3 using 3scale account data

Which issue(s) this PR fixes

https://issues.redhat.com/browse/THREESCALE-4857

Notes

This PR is an alternative to #1863

#1863 uses the plugins system of swagger ui to wrap and modify the components.

This PR uses a different approach: intercepts the response, injects the data to autocomplete and leaves swagger-ui do the rendering.
See responseInterceptor in https://swagger.io/docs/open-source-tools/swagger-ui/usage/configuration/

PROS:

• Cleaner code
• No DOM manipulation
• No need to maintain wrapped components
• It uses swagger default ui components

CONS:

• If some examples are already in the specification, they will be overwritten.
  I don't think it's a great problem, as we are autocompleting only the parameters using 3scale acccount data (from /p/admin/api_docs/account_data.json endpoint.).

Steps to reproduce

• Go to a Service's active docs section: apiconfig/services/2/api_docs
• Create a new spec using OAS v3 (you can use this example)
• Update the following templates at Dev Portal's Content section: /p/admin/cms/templates
  Documentation

<h1>Documentation</h1>

<p>Use our live documentation to learn about the Echo API</p>

{% content_for javascripts %}
    {{ 'active_docs.js' | javascript_include_tag }}
{% endcontent_for %}

{% include 'shared/swagger_ui' %}

---

shared/swagger_ui:

Replace the <script></script> section at the end of the document with:

<script type="text/javascript">
  (function () {
    var url = "{{provider.api_specs.first.url}}";
    var accountDataUrl = '/api_docs/account_data.json'


    SwaggerUI({
      url: url,
      responseInterceptor: function(response){return autocompleteOAS3(response, accountDataUrl)},
      dom_id: '#swagger-ui-container',
      supportedSubmitMethods: ['get', 'post', 'put', 'delete', 'patch'],
      apisSorter: 'alpha', // can also be a function
      operationsSorter: 'method', // can also be 'alpha' or a function
      docExpansion: 'list',
      transport: function (httpClient, obj) { ApiDocsProxy.execute(httpClient, obj) }
      });
  }());
</script>

[didierofrivia]

Could you point this to master in order to see all the changes?

[damianpm]

Could you point this to master in order to see all the changes?

@didierofrivia
Done!

[damianpm]

@josemigallas @didierofrivia
then you agree this is a better option than #1863 ?

[josemigallas]

@josemigallas @didierofrivia
then you agree this is a better option than #1863 ?

It looks simpler and better

[didierofrivia]

I think this is the right path to follow, you can close #1863 if you want 👍

[didierofrivia]

I left a final minor comment, but the most important thing is that it matches the current behaviour 100%. If that's the case, it's good to go!

[didierofrivia]

Squash the commits before merging.

[thomasmaas]

@damianpm be carefull to reference the correct jira in branch name. as now parent issue was moved to ready for testing