Document regarding Area(2D)'s priority being irrelevant for manual intersection queries

While the documentation does report that priority is relevant to processing, it is way too easy to assume that processing priority also applies to intersection queries, however as far as implementation goes this is not the case. At least regarding Area2D anyway, I haven't checked 3D Areas as closely but I would make the assumption the rules on this case are intended to be consistent. (correct me if I'm wrong on that) If this isn't intended I can make an issue on the main repo for the subject, but if it is intentionally ignoring priority I think it be appreciable to notify this behavior on the documentation, given it appears irrelevant to all intersection queries, I suggest marking it off on Area.priority instead of in each intersection query since that's where its relevant.