What problem does this address?

The new @wordpress/theme package in #72305 adds a number of new design tokens which are intended to be consumed through generated CSS properties. While these are documented, we can't take advantage of any existing developer tooling to ensure correct use of valid tokens / CSS properties.

What is your proposed solution?

In order to improve developer experience, we should add additional Stylelint and/or ESLint tooling to ensure correct references to CSS properties generated by the @wordpress/theme package.