Identify various flag labels and bit constants

[Rangi42]

After this, only four labels will be unidentified:

• wcd6d (110 uses)
• wcf91 (171 uses)
• wd0b5 (56 uses)
• wd11e (163 uses)

Of course, there are still many non-label constants left to be identified. In particular, flag bits and meaningful RAM values that should be going in the new ram_constants.asm file.

[Rangi42]

Some notes on naming choices:

• wMiscFlags is distant from all the wStatusFlags* locations, so it should have its own name.
• wStatusFlags5 corresponds to pokecrystal's wStateFlags, but after discussion with @dannye , I'm leaving it as one of the wStatusFlags* since there are so many more in gen 1 than gen 2.
• Arguably some of the wStatusFlags* labels could be more specific, e.g. wRodFlags for wStatusFlags since three of its bits are for getting the Rods, or wWarpFlags for wStatusFlags5 since four of its bits are warp-related, but overall they're just too generic. (I also considered using more generic names like wMiscFlags, wEngineFlags, wGameFlags, wModeFlags, etc, but assigning them to particular bytes felt really arbitrary.)
• On the other hand, I called it wMovementFlags instead of wStatusFlags8 because engine/battle/wild_encounters.asm checks the whole value at once with and a, implying that all its flags should be related somehow.
• wUnusedFlag is a generic name; unlike wUnusedLinkMenuByte, wUnusedCreditsByte, wUnusedAlreadyOwnedFlag, etc, there's no connection between its two usages (clearing it on the title screen and when trading Pokemon).

[Rangi42]

@dannye @vulcandth I think all that really needs reviewing are the constants and wram files; the rest are just many uses of those new constants+labels.

[Rangi42]

@dannye Okay, this is ready. I'm open to changing some of the wStatusFlags* names but don't really see better non-generic options.

[dannye]

Awesome.

[Rangi42]

@dannye Thank you for your review comments! They should all now be addressed.

[dannye]

LGTM. This is pretty great, thanks for doing it.