fix: create options api for cors preflight request.

[kaichaosun]

Description

CORS request triggers an Options request to same endpoint. More context.
The changes here will fix send REST API request from web browser to local nwaku node.

Changes

• Access-Control-Allow-Headers set to Content-Type, this is needed to fix error Reason: header ‘content-type’ is not allowed according to header ‘Access-Control-Allow-Headers’
• Options method enabled in relay rest api.

[github-actions]

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:2598-rln-v2-true

Built from dc496bb

[NagyZoltanPeter]

Awesome!!! Thank you for this extension!
Should we have similar OPTION method handlers for all the enpoint paths?

[kaichaosun]

@NagyZoltanPeter We can add OPTIONS for other endpoints when people requesting it, not sure if it's a best practice though. Prefer not adding too much boilerplate code.

[NagyZoltanPeter]

@NagyZoltanPeter We can add OPTIONS for other endpoints when people requesting it, not sure if it's a best practice though. Prefer not adding too much boilerplate code.

@kaichaosun Do you think it worth to make some more generic solution for it? I think of, in case allow-origin is configured we should auto add OPTION to each installed endpoint?
Current Presto implementation supports a chain of middleware callbacks can be installed, within such we could handle OPTION calls by checking valid paths.

[Ivansete-status]

LGTM! Thanks!
@kaichaosun - let's make sure all tests pass before merging :)
The only ones that we expect to fail are the js-waku jobs, which will be fixed soon

[kaichaosun]

@NagyZoltanPeter A generic and auto solution for all endpoints would be great. I will create an issue to track it.

[kaichaosun]

Force pushed for verified commit. @Ivansete-status