String literals in node inputs/outputs now auto-fixed

When community node developers use raw string literals like 'main' in their node's inputs and outputs properties, they bypass type checking entirely. Typos or renamed connection types slip through undetected until runtime.

The @n8n/eslint-plugin-community-nodes plugin now includes a rule that catches these string literals and suggests — or auto-fixes — the appropriate NodeConnectionTypes enum value instead. The rule derives its mapping directly from n8n-workflow at runtime, so it stays synchronized as new connection types are added without requiring updates to the rule itself.

In the eslint-plugin-community-nodes package, the rule is enabled at the error level across both recommended configurations. Developers running the linter against their node code will see immediate suggestions to replace hardcoded strings with the enum reference, and can apply fixes automatically with eslint --fix.

This is part of a broader push to enforce consistency and catch bugs early in the node development workflow.