Regression migrating from Standard to Enterprise Tier: --runtime-version not supported with app deployment create

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

See my Workflow deployment at https://github.com/ezYakaEagle442/azure-spring-apps-petclinic-mic-srv/blob/azure/.github/workflows/build-deploy-apps-staging-CLI.yml#L467

  DEPLOYMENT_RUNTIME_VERSION: Java_11
  DEPLOYMENT_CPU: 500m
  DEPLOYMENT_MEMORY: 1Gi
  DEPLOYMENT_INSTANCE_COUNT: 1
  
          az spring app deployment create \
            --name $DEPLOYMENT_NAME \
            --app ${{ env.VETS_SERVICE }} \
            --service ${{ env.AZURE_SPRING_APPS_SERVICE }} -g ${{ env.RG_APP }} \
            --instance-count ${{ env.DEPLOYMENT_INSTANCE_COUNT }} \
            --cpu ${{ env.DEPLOYMENT_CPU }} \
            --memory ${{ env.DEPLOYMENT_MEMORY }} \
            --version ${{ env.DEPLOYMENT_VERSION }} \
            --runtime-version ${{ env.DEPLOYMENT_RUNTIME_VERSION }} \
            --skip-clone-settings

--runtime-version doesn't support for Enterprise tier Spring instance.

Expected behavior
The Workflows & az spring app deployment create should run as is with Standard tier

Screenshots
N/A

Additional context
see also https://github.com/MicrosoftDocs/azure-docs/issues/102826#issuecomment-1355201936

从 .github/workflows/build-deploy-apps-staging-CLI.yml 中的 az spring app deployment create 命令开始，针对报告的 tier 转换复现 --runtime-version 错误。跟踪该命令对 Standard 和 Enterprise 实例的处理，然后验证 deployment workflow 是否按照预期的 runtime-version 行为运行。