DevTools tells Babel to parse the source code using "jsx" and "typescript" plug-ins:
https://github.com/facebook/react/blob/ed6c091fe961a3b95e956ebcefe8f152177b1fb7/packages/react-devtools-extensions/src/parseHookNames.js#L446-L462

This will work for some simple usages of Flow, but syntax may diverge and cause the parsing to fail.

Let's scan the source code for a `@flow` pragma and pass "flow" instead of "typescript" if one is found.

---

We should also add tests for both Flow and TypeScript to the test component pool:
https://github.com/facebook/react/tree/main/packages/react-devtools-extensions/src/__tests__/__source__
response
          .text()
          .then(text => {
            resolve(text);
          })
          .catch(error => {
            if (__DEBUG__) {
              console.log(`fetchFile() Could not read text for url "${url}"`);
            }
            reject(null);
          });
      } else {
        if (__DEBUG__) {
          console.log(`fetchFile() Got bad response for url "${url}"`);
        }
        reject(null);
      }
    });
  });
}
function findHookNames(
  hooksList: Array<HooksNode>,
  locationKeyToHookSourceData: Map<string, HookSourceData>,
): HookNames {
  const map: HookNames = new Map();
  hooksList.map(hook => {
    
    
    if (isNonDeclarativePrimitiveHook(hook)) {
      if (__DEBUG__) {