Fix #1819: Enforce order between script and script setup

[doug-wade]

Fixes #1819 . Adds a new tag type to the component-tags-order, script/setup.

[ota-meshi]

Thank you for this PR!
I wrote comments. I also want @FloEdelmann 's opinion on the option format.

[FloEdelmann]

I also think that existing options should continue to work, i.e. "script" should report both <script> and <script setup>.

I really like the CSS selector format suggestion by @ota-meshi. It's really clear and concise, and allows configuring e.g. <style scoped> above <style>, or any other individual use cases.

The object format is too noisy for me.

[ota-meshi]

@FloEdelmann Thank you for your opinion.

I really like the CSS selector format suggestion by @ota-meshi. It's really clear and concise, and allows configuring e.g. <style scoped> above <style>, or any other individual use cases.
The object format is too noisy for me.

I agree with you 👍

@doug-wade Can you change this PR so that user can specify a CSS selector as an option?
I think it's a good to add postcss-selector-parser to the dependency and use it to parse the selector.
https://github.com/postcss/postcss-selector-parser

If it's difficult to parse the CSS selector, could you add "script:not([setup])" and "script[setup]" as constant options?
I change the rule to be able to use CSS selectors when I have time.
I've used postcss-selector-parser in another project so I can implement it.

[FloEdelmann]

Looks good to me. Thanks for implementing the feedback!

@ota-meshi can you have another look?

[ota-meshi]

Thank you for changing this PR.
I will follow up about postcss-selector-parser later, so I commented on other things.

[ota-meshi]

LGTM! Thank you.