bevy_remote add resource request #17931
Description
What problem does this solve or what need does it fill?
Currently, there is no request in bevy_remote crate for getting a resource. In my case, another app needs to spawn entity based on the app state, which currently I have to store in the custom component to get it with "bevy/get".
What solution would you like?
I propose to introduce a "bevy/resource" for getting a resource with fully-qualified name like in the other requests.
What alternative(s) have you considered?
Workaround is to create a component and store resource value there (current state, in my case).