Add support for ARM bicep

With help of extension implemented in #36 user can now define a JSON file with ARM template. It would be good to extend that support to [bicep language](https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/overview?tabs=bicep)

Unclear yet. A possible implementation where user requests bicep in hubfile

```yaml
requires:
- azure
- arm
- bicep
```

Or arm can react on `*.bicep` files. Depends if before deployment `az bicep` must be specifically prepared. If yes then `requires[bicep]` is a valid approach as proper setup can be done during `hubctl stack configure`

> TODO: write DoD breakdown here

Start by reviewing the extension implemented in issue #36 and the hubfile configuration used by hubctl stack configure. Determine whether az bicep requires explicit preparation before deployment, then decide between requires[bicep] and reacting to *.bicep files. Define the missing DoD breakdown and verify the chosen behavior with a representative Bicep deployment.

Written by the indexing model from the issue text.