Closes#2940

Summary

Improves error messages for thevue/define-macros-order rule to distinguish between two distinct cases:

1. macrosNotAtTop: When a macro comes after non-macro statements (e.g.,console.log())
2. macrosUnordered: When macros are not in the correct order relative to each other

Motivation

Previously, the rule always reported: "X should be the first statement in<script setup>", which was confusing when multiple macros were out of order.
Users couldn't easily understand whether they needed to move a macro to the top or reorder it relative to other macros.

With this improvement, users get more specific feedback:

• "defineModel should be placed at the top of<script setup>" - when it's after a non-macro
• "defineModel should be above defineEmits" - when it's in the wrong order with other macros

This makes it much clearer what action is needed to fix the issue.

Changes

• Updated messages object with two new message types:macrosNotAtTop andmacrosUnordered
• ModifiedreportNotOnTop() function to detect whether the target statement is a macro from the order list
• UsesmacrosUnordered when the target is a macro,macrosNotAtTop otherwise
• Updated all test expectations to match the new behavior (42 tests passing)