Don't panic, do debug, when failing to remove component(s)

[CleanCut]

Resolves #698 by never panicking and always debugging when attempting to remove components (or remove_one a component) fails.

[mockersf]

I'm not sure this is the best way to deal with the unwrap in the remove case, as it will leave dangling components that the user think will be removed, and without notice at all if a logger is not setup...

Anyway I think it should at least be a warning instead of a debug as it leaves those components.
To have the log at debug level I think this components should be removed one by one when removing the bundle fails...

[cart]

Yeah I think falling back to one-by-one removal is a good idea. Its a bit more expensive (each removal is an archetype change), but it shouldn't be a super common case. Producing a debug log in that case should be enough for people to identify those cases when they care.

[CleanCut]

Shoot, I missed the fact that remove didn't remove any components if an error occurred.

I spent an hour on this, but I haven't been able to figure out a way to iterate through the bundle's types, though I learned quite a bit about TypeID and Any. Any hints?

More specifically, I see that you can get TypeIDs from T::type_info(), but I can't figure out how to go from a TypeID to an actual type.

[mockersf]

implemented the fallback in #719

[CleanCut]

Closing in favor of #719