Set node/no-unsupported-features version

Editor assessment

An ESLint configuration tweak—pinning the node/no-unsupported-features rule version—lands correctly as chore, since it alters tooling behavior for contributors only and should never reach a changelog or move the version. The subject names the exact rule, which is the level of specificity that makes housekeeping commits findable later, and it observes the lowercase, imperative, no-trailing-period conventions while staying brief. Two soft criticisms: a scope like lint or eslint would have made this filterable among the repository's many chores, and the absent body means the motivation—presumably aligning the rule's version check with the supported Node range—is left to inference from the diff. For a one-line config change, that omission is forgivable. Minimal, correctly typed, and unlikely to confuse anyone or anything downstream.