Fix OpenAPI and Swagger URLs and CORS

[suricactus]

Since the schema endpoint has been changed, we broke the integration on https://docs.qfield.org/reference/qfieldcloud/api/ . I overlooked the endpoint renaming.

@why-not-try-calmer was there any reason you rename endpoints?

[why-not-try-calmer]

Since the schema endpoint has been changed, we broke the integration on https://docs.qfield.org/reference/qfieldcloud/api/ . I overlooked the endpoint renaming.

@why-not-try-calmer was there any reason you rename endpoints?

Are you talking about https://github.com/opengisch/qfieldcloud/pull/722/files#diff-53c9c2dd0d12c371d3267292e547885a0189ce67b77ec67b3f6b590f140d959a? No, no reason I would have taken seriously in light of any evidence that this was breaking something. I think this PR benefitted from discussions plus a coworking session so I don't think I was trying to be original there.

[why-not-try-calmer]

I think it's not considered a good practice to use file extensions in urls, for the sake of not being hostage of an extension. But I am no expert in these conventions.

[suricactus]

Well, it depends. For the sake of backwards compatibility, it should have the extension for now.

[why-not-try-calmer]

Also I should point out that the url used in the documentation does point to a valid endpoint, any overlook notwithstanding. So isn't it simply the embedded JS being off?

[suricactus]

Also I should point out that the url used in the documentation does point to a valid endpoint, any overlook notwithstanding. So isn't it simply the embedded JS being off?

I would not prefer not to change it now.