feat(ban-operators)!: only run in pipe due to performance

Tested on a very large codebase with TIMING=1.  When checking every single CallExpression, it takes ~2.5 seconds.  When limiting to only inside of pipe, it drops off the top-10 slowest rules (less than 130ms).

Author: JasonWeinzierl

src/rules/ban-operators.ts

@@ -59,10 +59,10 @@ export const banOperatorsRule = ruleCreator({
     }
 
     return {
-      'CallExpression[callee.name]': (node: es.CallExpression) => {
+      'CallExpression[callee.property.name=\'pipe\'] > CallExpression[callee.name]': (node: es.CallExpression) => {
         checkNode(node.callee);
       },
-      'CallExpression[callee.type="MemberExpression"]': (node: es.CallExpression) => {
+      'CallExpression[callee.property.name=\'pipe\'] > CallExpression[callee.type="MemberExpression"]': (node: es.CallExpression) => {
         const callee = node.callee as es.MemberExpression;
         checkNode(callee.property);
       },

tests/rules/ban-operators.test.ts

@@ -55,6 +55,16 @@ ruleTester({ types: true }).run('ban-operators', banOperatorsRule, {
       `,
       options: [{ concat: true }],
     },
+    {
+      code: stripIndent`
+        // only within pipe
+        import { of, concat } from "rxjs";
+
+        // For performance reasons, we don't lint operators used outside of pipe.
+        concat(of('a'));
+      `,
+      options: [{ concat: true }],
+    },
   ],
   invalid: [
     fromFixture(