Fix FP S3403 (`different-types-comparison`): Ignore when comparing to `null` or `undefined` about sonarjs

[ericmorand-sonarsource]

Can we re-discuss this issue just to make sure that it is legit to add an exception?

• With types, if strictNullChecks is disabled, the rule never triggers because T is analogous to T | null | undefined in this case
• With types, if strictNullChecks is enabled, the rule never triggers because the compiler would not accept a variable of type T to be assigned null or undefined rendering the comparison body not reachable anyway
• Without types and without JSDoc annotations, the rule is never triggered because T is analogous to T | null | undefined in this case
• With JSDoc annotations, the rule is triggered when the JSDoc-declared type does not intersect with null, when compared to null, or undefined when compared to undefined. Hence, in this case, the issue comes from an incorrect JSDoc annotation instead of a rule false positive (for example, about https://peach.aws-prd.sonarsource.com/issues?resolved=false&rules=javascript%3AS3403&open=AYpEPL6JA8vuoRjT2MwJ, see https://github.com/WordPress/gutenberg/blob/trunk/packages/rich-text/src/types.ts)
• With pure JavaScript - no tsconfig.json file, the rule is never triggered.

[Wohops]

Migrated to Jira. New ticket number: JS-36