bevy dependencies updated to master

[Vrixyz]

I updated bevy dependency to target master, because I wanted to test a wasm build.

I'm not yet to a wasm build, but examples run fine.

• It might make sense to have a separate branch to prepare for future bevy versions ?

[Weasy666]

I am also in favor of this approach, as Bevy currently changes rapidly. So if one wants to experiment with the new Bevy features, they have to fork bevy_lyon and need to change the dependency.

[Nilirad]

I'm not sure about that feature. This crate used to track the master branch, but since the scope of this project is quite small, and bevy updates come quite often, I think that tracking only the releases can reduce the amount of effort to update the crate.

The best of the two worlds in my opinion could be to track bevy's master branch on a separate branch and keeping this master branch "clean". I see what can I do.