Bump entities to u128 to avoid collisions (#117)

[BoxyUwU]

Resolves #369
Also lets ecs_bench_suit run the add_remove bench for bevy_ecs

[CleanCut]

This seems to fix the issue in #369, at least I didn't reproduce the crash when running on macOS for several minutes. Without the change, the longest I was able to run the code in #369 before crashing was ~3.1s.

I can't speak to how this affects the other factors discussed in #117, but it seems like a very pragmatic resolution to current issue(s) and could still be replaced in favor of one of the other implementations in the future.

[cart]

I ran some perf tests earlier today using my ecs_bench fork. This has no effect on iteration performance (as expected), but adding entities/components does take a measurable hit:

• u32: 270 us
• u128: 357 us

First, I still consider 357us to be acceptable. This is still competitive with other frameworks, but it does take us much farther away from legion and hecs perf.

In the short term, I am inclined to merge this to resolve the collision bugs people are encountering. But the drop is significant enough that I will likely be more open to reverting to an incrementing index and adding a separate "stable" entity id for when its needed.

[zicklag]

In the short term, I am inclined to merge this to resolve the collision bugs people are encountering. But the drop is significant enough that I will likely be more open to reverting to an incrementing index and adding a separate "stable" entity id for when its needed.

That sounds like a good plan to me. This will keep things operating for users while we come up with a more long-term solution.