Troubling messages in build output

[DaveTryon]

Describe the bug

Building from the repo generates the following error messages:

WARNING in ../../node_modules/applicationinsights/out/AutoCollection/AzureFunctionsHook.js 51:40-72
Module not found: Error: Can't resolve '@azure/functions-core' in '.\node_modules\applicationinsights\out\AutoCollection'
 @ ../../node_modules/applicationinsights/out/applicationinsights.js 17:27-73
 @ ./src/ioc/setup-ioc-container.ts 32:33-63
 @ ./src/ado-extension.ts 40:30-66
 @ ./src/index.ts 40:42-68

WARNING in ../../node_modules/applicationinsights/out/AutoCollection/NativePerformance.js 42:44-89
Module not found: Error: Can't resolve 'applicationinsights-native-metrics' in '.\node_modules\applicationinsights\out\AutoCollection'
 @ ../../node_modules/applicationinsights/out/applicationinsights.js 16:26-71
 @ ./src/ioc/setup-ioc-container.ts 32:33-63
 @ ./src/ado-extension.ts 40:30-66
 @ ./src/index.ts 40:42-68

WARNING in ../../node_modules/diagnostic-channel-publishers/dist/src/azure-coretracing.pub.js 77:37-78
Module not found: Error: Can't resolve '@opentelemetry/instrumentation' in '.\node_modules\diagnostic-channel-publishers\dist\src'
 @ ../../node_modules/diagnostic-channel-publishers/dist/src/index.js 6:15-49
 @ ../../node_modules/applicationinsights/out/AutoCollection/diagnostic-channel/initialization.js 11:21-61
 @ ../../node_modules/applicationinsights/out/AutoCollection/CorrelationContextManager.js 5:18-64
 @ ../../node_modules/applicationinsights/out/applicationinsights.js 4:32-85
 @ ./src/ioc/setup-ioc-container.ts 32:33-63
 @ ./src/ado-extension.ts 40:30-66
 @ ./src/index.ts 40:42-68

Due to changing Node versions, I wasn't able to get an exact point where these were introduced, but they go back to at least #1156, which was merged more than a year ago. We've confirmed that telemetry is working as expected, but having errors in the build logs are far from ideal.

To Reproduce
Steps to reproduce the behavior:

1. git checkout main
2. git pull
3. yarn install
4. yarn build
5. Look at the log files--they scroll by quickly, but you can find the errors if you scroll back

Expected behavior

Logs should ideally be clean. There are 4 other warnings that also occur, but they're not called out as errors.

Screenshots

Here is a screenshot of the previously described errors, which also captures the color highlighting of the errors, as well as one of the warnings that doesn't get flagged as an error:

Context (please complete the following information)

• OS Name & Version: Happens on Win 11 22HS and on macOS Ventura 13.4

Are you willing to submit a PR?

Yes

Did you search for similar existing issues?

Yes

Additional context