`react-native autolink-windows` has regressed in speed since 0.65

[tido64]

Problem Description

react-native autolink-windows has regressed in speed since 0.65

Version	Time
0.64	3639ms
0.65	17793ms
0.66	22134ms
0.68	22488ms

Steps To Reproduce

n/a

Expected Results

react-native autolink-windows should take as long as 0.64 did.

CLI version

5.0.1

Environment

System:
    OS: Windows 10 10.0.22000
    CPU: (32) x64 AMD Ryzen Threadripper PRO 3955WX 16-Cores
    Memory: 117.20 GB / 127.86 GB
  Binaries:
    Node: 14.17.5 - C:\Program Files\nodejs\node.EXE
    Yarn: 3.1.1 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.4.1 - D:\react-native-test-app\node_modules\.bin\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK: Not Found
    Windows SDK:
      AllowDevelopmentWithoutDevLicense: Enabled
      AllowAllTrustedApps: Enabled
      Versions: 10.0.18362.0, 10.0.19041.0
  IDEs:
    Android Studio: Not Found
    Visual Studio: 16.11.32126.315 (Visual Studio Enterprise 2019)
  Languages:
    Java: 11.0.14 - /c/Program Files/Eclipse Adoptium/jdk-11.0.14.9-hotspot/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: ^0.64.3 => 0.64.3
    react-native-windows: ^0.64.25 => 0.64.27
  npmGlobalPackages:
    *react-native*: Not Found

Target Platform Version

No response

Target Device(s)

Desktop

Visual Studio Version

Visual Studio 2019

Build Configuration

Debug

Snack, code example, screenshot, or link to a repository

No response

[tido64]

cc @NickGerleman

[NickGerleman]

@chrisglein this seems like a pretty clear regression to build performance. Could you help me understand why you considered this item an enhancement?

[NickGerleman]

cc @Khalef1

@tido64 created this item as a bug, and it is pretty clearly one as well in my eyes. I would appreciate it if we didn't change the labels our engineers use when they file these. Especially given it feeds into tooling used to understand quality.