Preparing for the transition to an updated linter, standardizing the code base

[In1quity]

To apply new rules, linters or whatever and to do it as safely as possible, we first need to fix the tabs and linebreak-style (CLRF vs LF). Because this change breaks diffs and prevents PR from being checked properly.

ESLint Configuration Added:

• Added .eslintrc.json with comprehensive rules for code quality
• Applied strict code style standards across entire codebase

ESLint Wikimedia Rules Implemented:

• indent: ["error", "tab"] - Enforce tab indentation with SwitchCase support
• no-tabs: ["error", {"allowIndentationTabs": true}] - Disallow tabs except for indentation
• no-multiple-empty-lines: ["error", {"max": 1, "maxBOF": 0, "maxEOF": 0}] - Limit consecutive empty lines
• max-len: ["warn", {"code": 100, "tabWidth": 4, "ignoreUrls": true, "ignoreStrings": true, "ignoreTemplateLiterals": true}] - Enforce 100 character line limit
• linebreak-style: ["error", "unix"] - Enforce Unix line endings (LF)

Code Fixes Applied:

• 27 no-tabs errors: Removed all tab characters from code content (kept for indentation)
• 48 max-len warnings: Reformatted long lines to fit within 100 character limit
• 4724 linebreak-style errors: Converted all Windows CRLF line endings to Unix LF
• Multiple formatting issues: Fixed spacing, indentation, etc

Files Modified:

• .eslintrc.json: Added ESLint configuration
• index.js: Fixed line length and formatting
• All rater-src/*.js files: Applied consistent code style
• All Windows/Components/*.js files: Fixed formatting and line length

[NovemLinguae]

I'm not a big fan of max-len. That makes things easier for certain Linux users that use simple text editors without word wrapping, but makes things harder for the rest of us who have to hit enter a bunch of times when writing code comments, or fix the enters when we modify code comments. I don't think I want to merge a PR that has max-len in it.

linebreak-style seems like a good one to do. I would accept a PR that just had that rule added and its autofixes.

In general, smaller PRs are better. One PR per rule.