Fix ordering of lifecycle callbacks to match implementations

[lukewarlow]

Fix ordering of lifecycle callbacks to match implementations

connectedMoveCallback is moved before adoptedCallback.

Fixes #12016

• At least two implementers are interested (and none opposed):
  • Chromium (already implemented this)
  • Firefox (already implemented this)
• Tests are written and can be reviewed and commented upon at:
  • https://wpt.live/custom-elements/CustomElementRegistry.html
• Implementation bugs are filed:
  • Chromium: N/A
  • Gecko: N/A
  • WebKit: https://bugs.webkit.org/show_bug.cgi?id=281223 (Meta issue)
• Corresponding HTML AAM & ARIA in HTML issues & PRs: N/A
• MDN issue is filed: N/A
• The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

---

/custom-elements.html ( diff )

[annevk]

This seems to go further away from the lexicographical ordering desired by #3580. Is that still something we want to pursue?