Fix Containerapp YAML not reading workloadProfileName

[p-bouchon]

---

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

Related command

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?

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.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[jijohn14]

cli version 0.3.27 is creating invalid request payload by placing workloadProfileName outside properties

Hence got error:
cli.azure.cli.core.util: Response content:
cli.azure.cli.core.util: {"error":{"code":"InvalidRequestContent","message":"The request content was invalid and could not be deserialized: 'Could not find member 'workloadProfileName' on object of type 'ResourceDefinition'. Path 'workloadProfileName', line 1, position 95.'."}}

[p-bouchon]

cli version 0.3.27 is creating invalid request payload by placing workloadProfileName outside properties

Hence got error: cli.azure.cli.core.util: Response content: cli.azure.cli.core.util: {"error":{"code":"InvalidRequestContent","message":"The request content was invalid and could not be deserialized: 'Could not find member 'workloadProfileName' on object of type 'ResourceDefinition'. Path 'workloadProfileName', line 1, position 95.'."}}

Confirmed this to be an issue with the YAML file used, the key must be "workloadProfileName", not "workloadprofilename", all keys in the yaml file must be case sensitive

[zhoxing-ms]

@p-bouchon Could you please resolve these CI issues?