Implicit waitmovement 0

[mrgriffin]

Convenience macros for eliminating some explicit waitmovement 0s:

1. applywaitmovement: Fused applymovement and waitmovement 0.
2. Implicit waitmovement 0 for moverotatingtileobjects and turnrotatingtileobjects.

It is possible to create a variadic applywaitmovements macro, but I didn't think it would be practical because the lines would become very long. The remaining waitmovements are now mostly:

1. After special PlayerFaceTrainerAfterBattle (could not add an implicit waitmovement here because not all calls to that special immediately waitmovement).
2. After two or more applymovements.

Migration script for applywaitmovement: migrate_applywaitmovement.py.
WARNING: if there's complex control flow the linear "is it appropriate to fuse the waitmovement with the previous applymovement" might fuse when there's technically two or more applymovements and an explicit waitmovement 0 would be more idiomatic. It should not produce an incorrect result, but as always try comparing the sha1sum of your ROM before/after migration.

[mrgriffin]

Applied review suggestions: no more implicit argument to waitmovemet :)