Expose disabled linter rules

[giri256]

Fixes #3333

Summary

• Add --disable-linter-rules as a comma-separated string option for web-ext lint.
• Support the corresponding lint.disableLinterRules config value.
• Forward the value unchanged to addons-linter, which performs rule-name trimming and splitting internally.
• Preserve current behavior when the option is omitted.

Validation

• npx prettier --check src/program.js src/cmd/lint.js tests/unit/test.program.js tests/unit/test-cmd/test.lint.js
• npx eslint src/program.js src/cmd/lint.js tests/unit/test.program.js tests/unit/test-cmd/test.lint.js
• npx mocha tests/unit/test.program.js tests/unit/test-cmd/test.lint.js (69 passing)
• npm run build
• node bin/web-ext.js lint --source-dir tests/fixtures/minimal-web-ext --disable-linter-rules no-implied-eval --output json

[giri256]

CI audit note: the only failing context is build-nodejs-current, at its final npm run audit-deps step. Prettier, unit/coverage tests, both functional-test modes, Node next/experimental, and Windows all pass.

The audit is reporting newly blocking advisories in existing dependencies (adm-zip, brace-expansion, fast-uri, and shell-quote); this PR does not modify dependency files. The same current-job failure pattern is also present on the repository's open Dependabot PRs #3780 and #3779, so this is not introduced by this change.