DAPR Components are not compatible with Azure CLI

> Please provide us with the following information:
> ---------------------------------------------------------------

### This issue is for a: (mark with an `x`)
```
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```

### Minimal steps to reproduce
> deploy the services without bicep, but using az cli is not working due to the fact the dapr components.yaml files are not in the supported format

### Any log messages given by the failure
>

### Expected/desired behavior
> use the components.yaml to deplo with azue cli

### OS and Version?
> Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

### Versions
>

### Mention any other details that might be useful

> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.

Start by inspecting the repository's components.yaml files and the Azure CLI deployment path described in the issue. Reproduce deployment without Bicep using az CLI, then compare the component format with what the CLI accepts. Done means the components.yaml files can be used successfully in that deployment path.

Written by the indexing model from the issue text.