Bump in @azure/core-auth@1.6.0 to Node 18 was a breaking change and should have bumped major version

[jonthysell]

• Package Name: @azure/core-auth
• Package Version: 1.6.0
• Operating system:
• nodejs
  • version: 16.13.0
• browser
  • name/version:
• typescript
  • version:
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://docs.microsoft.com

Describe the bug
microsoft/react-native-windows relies on microsoft/ApplicationInsights-node.js which asks for @azure/core-auth@^1.5.0.

By introducing a breaking change in 1.6, it's now breaking internal customers downstream that have to maintain and support release branches on Node 16.

See the bug opened by affected customers of application insights: microsoft/ApplicationInsights-node.js#1274

See our bug: microsoft/react-native-windows#12711

To Reproduce
Steps to reproduce the behavior:

1. npx --yes react-native@0.72.6 init test72 --template react-native@0.72.6
2. npx react-native-windows-init

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
N/A

Additional context
N/A

[deyaaeldeen]

It is interesting though that appinsights still supports NodeJS v8. Yeah we thought a lot about situations like this when we designed our support policy:

The Azure SDK libraries for JavaScript will not be guaranteed to work on Node.js versions that have reached their end of life. Dropping support for such Node.js versions may be done without increasing the major version of the Azure SDK libraries.

We found that it is expensive to maintain our SDKs across the board to work on top unmaintained runtimes which are often susceptible to vulnerabilities and lack support for newer, critical features.

[xirzec]

This appears to be a duplicate of #28449