Swap (found) and (building) variables in 7A ulocate documentation

[limonovthesecond2]

The variables found and building are swapped in the last 4 examples of ulocate. This PR puts them in place

[cardillan]

The original version is actually correct. There's language target 7, which is the default, and in that one the function parameters are mapped as you expect. This file documents language target 7A, which needs to be explicitly selected (e.g. by #set target = ML7AS compiler directive); in this language target these functions return the located block/building instead of the found flag.

The difference between 7 and 7A is described here - perhaps it might be worded a little bit better.

As I've mentioned elsewhere, I plan to make changes to the syntax that will break at least some existing code, as part of this change I'll make the 7A target the default.

Additionally, these files (FUNCTIONS_*.markdown) are generated automatically based on the information in the MindustryOpcodeVariants.java file (there's a unit test that creates/modifies these files - it's probably an abuse of unit tests). Any changes you make to these files will get overwritten the next time the project is built.