{containerapp} Improve tests: Use same name foo for compose tests

[Greedygre]

All Containerapp Compose test cases have @serial_test() to mark test run serial.
Use following command run test cases which have been mark to serial.
azdev test azext_containerapp.containerapp --no-exitfirst --series -a '-m=serial'
I found when using different service name in compose file for compose tests, and then executed in parallel, will occur error (only occur this error with azdev test in parallel). So need to revert test cases back to use same name foo.

---

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? (pip install wheel==0.30.0 required)

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]

containerapp

[Greedygre]

Hi @yanzhudd
Could you please help to review this PR? Thanks.