ESLint rule flags unsorted community node options

Community node contributors submitting dropdown menus in their integrations will now receive immediate ESLint warnings when option lists aren't alphabetically sorted. The new rule, options-sorted-alphabetically, scans .node.ts files for type: 'options' parameters — covering resource dropdowns, operation selectors, and any other options fields — and flags misordered entries using locale-aware comparison that handles non-ASCII characters correctly, including Spanish and Portuguese labels.

This addresses the most frequently flagged issue in community node reviews, where maintainers previously had to manually catch and request fixes for alphabetically unsorted dropdowns. The rule is set to warn in both recommended config profiles, allowing contributors to self-correct before submission. Since it's a lint rule rather than a build blocker, existing nodes aren't affected — only new and modified nodes will receive the warning during development or CI checks.