docs(yardmap): Some refactoring

[badosu]

No description provided.

[badosu]

cc @sprunk @robertthepie bringing over discussion on:

• Improve yardmap tiles documentation #2302 (comment)
• Improve yardmap tiles documentation #2302 (comment)

sprunk I still have absolutely no idea what stackable means (more reason to try and improve this documentation I guess), can you explain like im 5?

[badosu]

@robertthepie Do you want to submit your prose to be included on this PR? Feel free to add some ```suggestion

[sprunk]

Could be confusing to say "anything else" before all options were mentioned (h was previously above this line but is now below and in a different section).

[sprunk]

Will produce ELI5 pictures for stackables soon (perhaps even to put in the article)

[sprunk]

Will produce ELI5 pictures for stackables soon (perhaps even to put in the article)

Say we've got an oooo unit and we're trying to put a unit with some y on the left, some o at the bottom and some s at the top on that:

The y on the left can go on top of o.
The o at the bottom cannot go on top of o.
The s CAN go on top of o:

---

Now let's try the reverse!

The 'o' can go on top of the y on the left.
The o cannot go on top of o.
The o CANNOT go on top of s.

Something unexpected I noticed is that s doesn't seem to quite work like an o but like a c, i.e. it's becomes open if you open the yardmap. I have no idea if this is by design or not.