Add CORS header configuration for BRP RemoteHttpPlugin

[villor]

What problem does this solve or what need does it fill?

To fully utilize the BRP functionality using web hosted tools, we need a way to set the Access-Control-Allow-Origin header in the responses.

Without being able to set that header, we would have to resort to reverse proxies to get around the issue.

What solution would you like?

Add a with_cors method to RemoteHttpPlugin. The method would ensure that Access-Control-Allow-Origin is added to all responses, with the origin provided as a param.

What alternative(s) have you considered?

We could add the option to set any headers during setup. But I don't know if that is really needed.

Additional context

See bevy_react_inspector which currently needs a reverse proxy to function.

[JMS55]

I'd rather a custom header in general vs specifying cors specifically.

[spacemen0]

I think with_cors probably make sense? Enabling cors might be the most common in terms of user cases.

[villor]

Ideally, we would have both configurable headers and a with_cors for conveniency IMO.

I also believe cors will be the most common use case by far. So an initial solution could be to implement just that method.

[spacemen0]

I'm new to bevy but I think I can try working on this