v-col 'cols' prop shift from string to number in Vuetify 3

Goal

Determine whether the numeric‑only cols API in Vuetify 3 yields a measurable performance benefit over the legacy string syntax used in Vuetify 2, and assess the impact on backward compatibility.

Constraints & Uncertainty

• Current projects may still use cols="12" strings; these trigger deprecation warnings and could break in a future minor release.
• The documented change removes runtime string parsing, but the actual rendering overhead reduction is unverified for typical grid sizes.
• Vuetify 3.5 and beyond may drop string support entirely, yet the migration path and tooling support are not fully documented.

Specific Questions

1. What is the projected timeline for the removal of string cols values in upcoming Vuetify releases?
2. Which tooling or lint rules can reliably audit existing v-col usages to flag string values for migration?
3. In a realistic workload (e.g., 1,000 v-col elements), how does frame rate or CPU usage differ between numeric and string cols values?