Fix x-id evaluation order so $id resolves consistently inside x-data

[joshhanley]

The Scenario

When x-id and x-data are on the same element, $id('name') inside the x-data expression returns a different id than $id('name') in descendants — breaking ARIA wiring that relies on them matching.

<div
    x-id="['a']"
    x-data="{ idFromData: $id('a') }"
>
    <p>From <code>x-data</code>: <strong x-text="idFromData"></strong></p>   <!-- a-1 -->
    <p>From <code>x-text</code>: <strong x-text="$id('a')"></strong></p>     <!-- a-2 -->
</div>

The Problem

data runs before id in the directive order. So $id('a') inside x-data finds no _x_ids on its ancestor yet and falls back to the global counter (returns 1). Then x-id runs and calls findAndIncrementId again (returns 2), which becomes the actual id root. Descendants resolve a-2 while the x-data scope holds a-1.

The Solution

Swap id ahead of data in directiveOrder so the id root is registered first.

x-id only takes a static array of name strings, so it doesn't need x-data scope to evaluate. Docs, tests, and real-world usage all use this pattern.

Fixes #4817

[calebporzio]

great!