macOS 11 Big Sur M1 chip issues

Local debugging won't work: https://github.com/adobe/aio-cli-plugin-app/issues/322

`node.js` itself should work under `Rosetta 2`, a native binary is pending: https://github.com/nodejs/build/issues/2474

If any of our tools/libs compile `native extensions`, there might be issues possibly.

`deasync` uses native extensions:
```
$ npm ls deasync
@adobe/aio-cli@5.0.1 /Users/shazron/Documents/git/adobe/aio-cli
└─┬ @adobe/aio-cli-plugin-app@5.0.2
└─┬ parcel-bundler@1.12.4
└── deasync@0.1.21
```

`fsevents` uses native extensions:
```
$ npm ls fsevents
@adobe/aio-cli@5.0.1 /Users/shazron/Documents/git/adobe/aio-cli
├─┬ @adobe/aio-cli-plugin-app@5.1.1
│ ├─┬ @adobe/aio-lib-runtime@1.2.0
│ │ └─┬ webpack@4.44.2
│ │ └─┬ watchpack@1.7.5
│ │ └─┬ watchpack-chokidar2@2.0.1
│ │ └─┬ chokidar@2.1.8
│ │ └── fsevents@1.2.13
│ ├─┬ chokidar@3.4.3
│ │ └── fsevents@2.1.3
│ └─┬ parcel-bundler@1.12.4
│ └─┬ @parcel/watcher@1.12.1
│ └─┬ chokidar@2.1.8
│ └── fsevents@1.2.13
└─┬ jest@24.9.0
└─┬ jest-cli@24.9.0
└─┬ @jest/core@24.9.0
└─┬ jest-haste-map@24.9.0
└── fsevents@1.2.13
```

Start by reproducing the local debugging failure from the linked aio-cli-plugin-app issue on a macOS 11 M1 system. Run the two `npm ls` commands shown in the issue to inspect native-extension dependencies, then compare behavior under Rosetta 2 and native execution. Done means local debugging and the affected CLI tooling work on the target system, or the incompatible dependency is identified and documented.

Written by the indexing model from the issue text.