Respect `"use no memo"` - exclude components and hooks from the report

[kachkaev]

I added "use no memo" in a couple of places where I do unconventional tricks with hook deps. Example:

export function useMyCustomHook(
  firstArgument: FirstArgument,
  deps: React.DependencyList,
): void {
  "use no memo";
  
  React.useEffect(() => {
    // logic around firstArgument
  }, [
    callback,
    // eslint-disable-next-line react-hooks/exhaustive-deps -- ...deps are added by design
    ...deps,
  ]);
}

This hook cannot be memoised by design so I annotate it with "use no memo". The extension still marks my custom hook with 🚫 and lists it in the report amongst 🚫 failed cases. It'd be great to treat disabled memorisation differently. WDYT?

Possibly related: #67

[blazejkustra]

Hey @kachkaev, I opened #77. Opt-outs now land in a separate "skipped" bucket ⏭️ instead of being counted as failures.

One caveat: babel-plugin-react-compiler only emits CompileSkip when the opted-out function actually compiles cleanly. If it has the directive and fails to compile, the plugin still emits CompileError and never emits CompileSkip. I'd rather not re-implement directive detection on our side to work around it. So opt-outs that compile cleanly will show as skipped; opt-outs that don't compile will still surface as failed. If your case is the latter, that's probably an upstream issue.