What and why?

This PR adds support for Azure Web App deployment slots in the AAS (Azure App Service) instrumentation commands. Previously, the CLI only supported instrumenting main Web Apps, but Azure allows creating deployment slots for staging, testing, and blue-green deployments. This enhancement enables users to instrument and uninstrument specific deployment slots.

Also, to be more clear on language, opts for 'Web App' as the resource type instead of the more generic 'App Service'. I'll make a follow up PR to also update the command to have web-app as an alias for the scope

I also discovered a bug in the windows runtime detection which I've fixed, where sometimes a nodejs app will not be properly identified since it uses the weird convention of requiring a specific env var to be set. Sometimes, the netFrameworkVersion is specified even for other runtimes, so we should check the other runtimes first, and then check the netFrameworkVersion as a last resort.

How?

• Added a new --slot parameter to specify the slot name for instrumentation
• Updated the WebApp interface to include an optional slot property
• Modified Azure resource ID parsing to handle slot-specific resource paths (e.g., /sites/{name}/slots/{slotName})
• Updated all Azure API calls to use slot-specific methods when a slot is specified (e.g., getSlot, restartSlot, updateApplicationSettingsSlot)
• Added utility functions renderWebApp and resourceIdSegment for consistent display and resource path generation
• Updated command descriptions and documentation to reflect "Web App (or slot)" terminology
• Updated the env var fetching to happen at the beginning which allows them to be properly used for the windows node case.

Validation

I've done some thorough manual testing with web apps and validating that telemetry comes through, and I've also added/updated the unit tests in the plugin.

Review checklist

• Feature or bugfix MUST have appropriate tests (unit, integration)