[Container app] az containerapp connected-env certificate upload: Fix unknown properties certificateKeyVaultProperties

[Greedygre]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

azure.cli.core.azclierror.HTTPError: Bad Request({"type":"https://tools.ietf.org/html/rfc7231#section-6.5.1","title":"One or more validation errors occurred.","status":400,"traceId":"00-848eb3ce4a2427b888220c7cafca3797-2760e522042a3bcf-01","errors":{"$.properties":["Unknown properties certificateKeyVaultProperties in Microsoft.KubeEnvironments.WebApi.Views.Version20231101Preview.CertificateView are not supported"]}})

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @Greedygre,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Container app