fix(perf): Use fork of bevy_simple_tilemap with rayon par_iter feature disabled until PR merged.

[MaxCWhitehead]

This fixes fishfolk/jumpy#841, can switch back to original crate once fix is merged upstream of fork.

Change we are introducing is here: forbjok/bevy_simple_tilemap@master...MaxCWhitehead:bevy_simple_tilemap:v0.11.0
Gates rayon behind feature flag, which we do not use.

[MaxCWhitehead]

@zicklag might have made a mess of this PR haha, I fixed the bevy version having been 0.10.0 in fork vs 0.10.1, should fix the previous minimal dependencies error. I couldn't figure out how to rerun the github actions, perhaps I don't have permission?

So I pushed an empty commit to trigger, then I was going to force-push it out before merging, so I disabled auto-merge. It seems actions aren't running though. Going to remove that empty commit, and perhaps you can re-enable auto-merge and re-run actions.

[zicklag]

Ah, yeah, it's because it's your first contribution to bones it makes me manually approve any changes you make before CI will run. I'll re-approve and re-auto merge.

[zicklag]

Actually it looks like there's another issue with CI here. I'll look at it real quick.

[MaxCWhitehead]

Hmm, appears to be the same one. I tried to run minimal version check command locally and did not reproduce the same error, not sure why exactly, thought that may have been the issue, but guess not. Might have to mess with it more. Let me know if you have any ideas on what commands / tools to use locally to diagnose this type of thing.

[zicklag]

It has something to do with the Rust version being different for those two CI jobs, because it has to use nightly Rust to enable certain unstable flags for miri and the minimal deps check.

This isn't the fault of your PR, so I'll just override the the CI job to let this merge.

[MaxCWhitehead]

Ah ok, gotcha.