Sprite Priorities and Conflicts is badly written / not fitting the documentation formal style

[avivace]

Feedback by @Bananattack on Discord:

There's some new commentary about certain topics like "Sprite Priorities and Conflicts", that feels much less clear than the original Pan Docs. I think the rules could be spelled out in much more clear and concise way if we plan to rewrite it. There's a bunch of parts added about specific emulators (BGB) that while handy I don't think should be in a reference doc about the hardware. The parenthesized point about z-fighting feels extraneous. The new edit still no longer mentions what "higher priority" means. It could say that entries are decided by their order in the OAM table, and that entries with a lower index have higher priority (the old document actually does mention this, but if you don't know $FExx addresess refer to OAM you may miss it). The basic rules should really be clearly summarized in a few sentences at most, instead of 4 paragraphs like it is now, or potentially some bullet points + elaboration below. If given time I can send an edit that makes this much clearer.