Update and integrate API documentation

[markbrough]

Is your feature request related to a problem? Please describe.

There are a few issues with the API documentation at the moment:

• it runs as a set of Sphinx scripts, separate from the rest of the front end query builder, so the user experience is a bit jarring
• everything has to be manually written from scratch each time
• it is not always kept up to date as API routes etc change (see Update Documentation to include XLSX options as well as CSV #355 and Generate API docs from docstrings #98)

Describe the solution you’d like

• integrate with existing NuxtJS app (also then potentially simplifying translation)
• generate basic documentation from API docstrings

Describe alternatives you’ve considered

Leaving everything more or less as it is (i.e. just updating Sphinx)

Additional context

Custom solution:

• https://www.storyblok.com/tp/api-documentation-storyblok-nuxt-js-netlify-and-github
• https://github.com/storyblok/storyblok-docs

Using Swagger:

• https://github.com/Elevista/nuxtswagger

[ghost]

I don't have any immediate thoughts on good technical solutions but certainly the problems make sense.

I'm not sure if static help pages need to be in NuxtJS tho - I see that as having strengths for interactive pages (eg the query builder front page). Help pages could be kept simple and just be served by flask, which handily just had I18N options added.