Comment 11 for bug 1850473

Okay, my new plan is to:

* redo this work next week, after feature freeze
* configure eslint to prefer a different switch/case format (that one made me cringe a little too, Mike!)
* only change == to === in code that is under some type of automated test. I will note that this rule was in the old codelyzer implementation, so it is not new, just... it's been inactive for a while?

My outstanding questions are:
* the discussion on bug 2017793 proposes that we wait until Angular 16 before adding accessibility rules. I'm not opposed to adding them as part of this work, but just want to confirm that it's what we prefer.
* what more publicity is required?