Add signalling utils to bevy_matchbox

[garryod]

Adds some utils for creating a MatchboxServer to a bevy app as a Resource.

stop_server is currently a no-op, need to figure out how best to kill a bevy task - probably scopes. Realised this is also an issue with our regular socket behaviour

[johanhelsing]

stop_server is currently a no-op, need to figure out how best to kill a bevy task - probably scopes. Realised this is also an issue with our regular socket behaviour

For the socket i think it would probably make most sense to either support dropping the socket, or have a channel we send to that will make the future clean up and stop.

[garryod]

stop_server is currently a no-op, need to figure out how best to kill a bevy task - probably scopes. Realised this is also an issue with our regular socket behaviour

For the socket i think it would probably make most sense to either support dropping the socket, or have a channel we send to that will make the future clean up and stop.

Have opted to move the Task handle into the Component / Resource such that when they're dropped the task is terminated

[garryod]

Also made the choice to remove the feature gate as target specific features are not yet supported (see: rust-lang/cargo#1197). An alternative method is to add a build script which provides an appropriate error message when someone tries to use a feature incompatible with the target, but this doesn't play particularly well with other tooling

[simbleau]

LGTM. Any bevy_matchbox improvements are good to me.

[simbleau]

@johanhelsing ?

[simbleau]

@johanhelsing approval?

[johanhelsing]

Great :)