[Refactor] no-invalid-html-attribute: sort HTML_ELEMENTS and messages

[Primajin]

Sorting things help me anticipate what the next item in the list will be and allow me to spot missing values, e.g. when there was no strong after strike I'd directly see that it would be missing.

Totally fine to do it in a separate PR, just makes this one harder to review :-)
Originally posted by @ljharb in #3174 (comment)

This is a pure chore commit - it only re-arranges/sorts the code - no additions or removals.

[codecov-commenter]

Codecov Report

Merging #3182 (541ea43) into master (4c668b3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3182   +/-   ##
=======================================
  Coverage   97.55%   97.55%           
=======================================
  Files         120      120           
  Lines        8288     8288           
  Branches     2982     2982           
=======================================
  Hits         8085     8085           
  Misses        203      203           

Impacted Files	Coverage Δ
lib/rules/no-invalid-html-attribute.js	96.71% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4c668b3...541ea43. Read the comment docs.

[ljharb]

(I renamed it because the word "chore" is wildly inappropriate; chores are miserable things that you're forced to do by an authority figure :-) maintenance tasks and refactors are good things, and shouldn't invite that kind of connotation)

[Primajin]

Hahaha 😅 OK! 👍🏻
I wasn't sure how much folks are into Conventional Commit style here. Refactor sounds much much better

[ljharb]

That tooling is great, but unfortunately the actual style is terrible, and offers no way to configure it.