Bevy Engine

This release is big! We abstracted out all I/O and renet dependency. We will continue to provide first-party integration with renet via bevy_replion_renet.

But now users can write their own integration with other messaging libraries. Refer to the documentation for instructions on how to do it, the process is very simple. See bevy_replicon_renet as an example.

This also opens up the possibility of simultaneously using multiple messaging libraries on the server, as long as the client identifiers they provide are unique.

See the changelog for a full list of changes.

📦bevy_replicon 📦bevy_replicon_renet