Deploy an Azure App Service: support Flex Consumption plans via OneDeploy

[HuyPhanNguyen]

Background

The built-in "Deploy an Azure App Service" step fails with HTTP 404 when the target Function App runs on an Azure Flex Consumption plan. Calamari uploads the package by POSTing to the Kudu /api/zipdeploy endpoint, which Flex Consumption plans don't expose. Microsoft now recommends Flex Consumption over the classic Consumption plan and is deprecating the classic plan on 2028-09-30, so more customers will hit this over time.

Results

Detects the App Service Plan SKU tier at deploy time and, when it's Flex Consumption, uploads zip/nupkg packages through the OneDeploy (/api/publish?type=zip) endpoint with an application/zip content type instead of ZipDeploy.

Fixes HPY-20.

Before

Deploying a zip/nupkg package to a Flex Consumption Function App POSTs to https://<scm>/api/zipdeploy and returns 404 (Not Found), so the step fails.

After (this PR)

The step resolves the plan tier (App Service Plan '...' is on the 'FlexConsumption' tier (SKU 'FC1')), POSTs to /api/publish?type=zip, polls to completion, and the deployment succeeds. Non-Flex plans are unaffected and still use /api/zipdeploy.

Both captured live against the same real Flex Consumption Function App, same package — only the Calamari build differs.

Testing

• Unit: extended PackageProviderFactoryFixture to assert the upload endpoint, sync/async mode, and content type for the Flex and non-Flex cases across .zip/.nupkg/.war/.jar.
• Live end-to-end against a real Azure Flex Consumption Function App (dotnet-isolated 8.0), deploying via the built-in step with this build injected through Octopus.Calamari.Executable:
  • Before: POST .../api/zipdeploy?isAsync=true → 404 (Not Found), deployment fails.
  • After: App Service Plan ... is on the 'FlexConsumption' tier (SKU 'FC1') → POST .../api/publish?type=zip → deployment succeeds.

Automated Tests

• Run full chain build (PRs targeting main release/* branches only)

Pre-requisites

• I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
• I have considered informing or consulting the right people, according to the ownership map.
• I have considered the appropriate target version for this PR.
• I have considered appropriate testing for my change.
• I have considered manually testing my changes on a branch instance to check correctness, stability and performance on Octopus Cloud.
• I have considered safety nets to reduce any time-to-recovery for my change.