Samples deploy Durable Task Scheduler with Dedicated SKU; switch Bicep to Consumption

[greenie-msft]

The samples in this repo currently deploy Azure Durable Task Scheduler (DTS) using the Dedicated SKU.

Dedicated is expensive and slow to deploy, which makes the samples painful for quickstarts and developer evaluation.

Expected behavior
All sample deployments should default to the Consumption SKU instead, because it is the appropriate choice for samples/quickstarts and is cheaper + faster to provision.

What to change
Update the Bicep templates that deploy Microsoft.DurableTask/schedulers to:

• Set the DTS SKU name to Consumption
• Do not set sku.capacity when using Consumption (capacity applies to Dedicated; Consumption has no capacity).

Per the resource schema, sku.name supports 'Consumption' | 'Dedicated', and sku.capacity is a scale/capacity setting that should not be used for Consumption.