Create public documentation for developer expectations when using each supported service target or language

[wbreza]

Today our documentation is limited when it comes down to converting your own application to be azd compatible.

Current Docs:

• Make your project azd-compatible
• Manage Environment Variables

We should have a dedicated page/section for the following:

• Dedicated page for each support language
  • Outline the lifecycle for each language and the underlying commands run for each lifecycle, restore, build, package & deploy. For example, during build of javascript/typescript applications call npm run build.
  • Specifically call out any noop operations
• Resource group / resource discoverability
  • More / better docs around azd-env-name and azd-service-name and other resource resolution strategies
  • Override with config
  • Override with environment variables
• Each service target (containerapp, appservice, aks, etc)
  • Expected IaC outputs / environment variables
  • Additional configuration to override environment variables
  • Commands run based on configuration (kubctl, helm, kustomize)
  • REST calls made against Azure control plane

[rajeshkamal5050]

Giving us more time to work on the doc. Moved this to the next milestone @gkulin