refactor: deprecate events not comply with Vue event naming rules

[susnux]

☑️ Resolves

Deprecate events which not comply with camelCase naming.
Only those two places have an invalid naming as normally only the update:MODEL event is scoped and other events just use camel case names like selectSomething (aka select-something) instead of select:something.

🏁 Checklist

• ⛑️ Tests are included or are not applicable
• 📘 Component documentation has been extended, updated or is not applicable
• 2️⃣ Backport to stable8 for maintained Vue 2 version or not applicable

[susnux]

/backport to stable8

[julien-nc]

Nice of you to keep the deprecated ones for a while 👍

[ShGKme]

Same as: #7059 (comment)

[susnux]

You might be right and I misinterpreted the docs.
But still we only have this two places, resize:list also makes not much sense it should rather be consistent with all other events we have (resize-list).

For interact:todo it might make sense if there are any other events for interaction, but its the only one so not sure.

[ShGKme]

You might be right and I misinterpreted the docs.

This might also be from the eslint-plugin-vue member's comments, where foo:barBaz is not considered camelCase, and : is considered a special case for update:* events (that are "never used without v-model/.sync directive").

IMO, this is only a personal opinion, and Vue documentation never says it directly.

I saw namespaced event names in many apps and good libs, which is a great thing for complex components.

There was added an additional option for ESLint rule for this case:
vuejs/eslint-plugin-vue#1321

[ShGKme]

But still we only have this two places, resize:list also makes not much sense it should rather be consistent with all other events we have (resize-list).

Agree as resize: is not a namespace.

For interact:todo it might make sense if there are any other events for interaction, but its the only one so not sure.

Yes, but future-proof.

[ShGKme]

So I'm fine with renaming in general.

But disagree with "With Vue 3 it is recommended ... only scope events for models" part

[DorraJaouad]

For interact:todo it might make sense if there are any other events for interaction

I am fine with renaming it bc now it conveys it as big feature whereas it's just one simple interaction and we don't have any plans to expand interaction.

[susnux]

Agree! Adjusted the changelog.

About the scoping: I do not have a problem with interact:todo but it seems its the only one where this is needed so we could also just use the plain event. But if you like then I revert that @ShGKme and add it as an exception to the eslint config.