Stack Deletion Action Should Not Require DenySettingsMode

In Deployment Stacks, DenySettingsMode is an input property for applying deny assignments. On deletion of the deployment stack, deny assignments are not applied and therefore DenySettingsMode is not a part of the deletion api. I recently had the below definition fail because it was expecting a DenySettingsMode parameter.

This should be all that is required for a stack deletion:

- name: Remove subscription-scope deployment stack
id: stack
uses: azure/bicep-deploy@v2
with:
type: deploymentStack
operation: delete
name: 'my-sub-stack'
scope: subscription
subscription-id: ${{ AZURE_SUBSCRIPTION_ID }}
location: 'eastus'
action-on-unmanage-resources: delete
action-on-unmanage-resourcegroups: delete

Start at the azure/bicep-deploy@v2 entry point for deploymentStack operations and trace validation for delete requests. Verify that deletion no longer requires DenySettingsMode while the other deletion inputs remain supported, then exercise the subscription-scope example to confirm it succeeds without that parameter.

Written by the indexing model from the issue text.