Rename vue/component-tags-order to vue/block-order

[FloEdelmann]

Fixes #2214.

[ota-meshi]

Sorry for the late reply. I am busy with office work.
The pull request change looks good to me! However, it seems to change the configuration, so I will merge it when we start working on v10.

[FloEdelmann]

It should not be a breaking change though, I only renamed the rule and followed the deprecation procedure. The breaking change would be to remove the old rule completely.

[ota-meshi]

In my opinion adding a rule to a shared configuration is marked as a breaking change. (It's not a breaking change if we reduce the rules)

https://github.com/eslint/eslint#semantic-versioning-policy:~:text=eslint%3Arecommended%20is%20updated%20and%20may%20result%20in%20new%20linting%20errors%20(e.g.%2C%20rule%20additions%2C%20most%20rule%20option%20updates)

Users using shared configuration and turning off the vue/component-tags-order rule will receive the new warning unless they turn off the vue/block-order rule.

It's not a breaking change if we don't add vue/block-order to the shareable config.

[FloEdelmann]

Ok, should I then add the (deprecated) vue/component-tags-order rule back to the recommended configs and remove vue/block-order from the configs for now? We should then change it when we remove the vue/component-tags-order rule completely.

[ota-meshi]

Ok, should I then add the (deprecated) vue/component-tags-order rule back to the recommended configs and remove vue/block-order from the configs for now?

Yes. I think we need to do that to release this PR with v9 👍

[ota-meshi]

LGTM! Thank you!