FunctionApp template defaults are wrong or missing

[function-app-create-dynamic](https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.web/function-app-create-dynamic/main.bicep)

### Issue Details
Looking at how we default a number of our tools and portal, I can spot some issues I'd like to fix here and in the corresponding quickstart doc.

1. defaults to windows, but should be linux
```bicep
param kind string = 'functionapp,linux'
```

2. missing a number of the language runtimes - has 3 but should be

```bicep
@allowed([
  'dotnet', 'dotnetcore', 'dotnet-isolated', 'node', 'python', 'java', 'powershell', 'custom'
])
```

3. no runtime-version is specified.  what happens?  do we choose and choose latest?  probably should have them set it and have notes pointing to supported versions

```bicep
param runtimeName string
param runtimeVersion string
param runtimeNameAndVersion string = '${runtimeName}|${runtimeVersion}'
```

Generally I feel this should have the exact same defaults as the bicep module for AZD, or we should in fact use it. It's about to go into the bicep registry:
https://github.com/Azure/azure-dev/blob/main/templates/common/infra/bicep/core/host/functions.bicep

### Repro steps (*if necessary, delete otherwise*)
1. Follow the [quickstart](https://learn.microsoft.com/en-us/azure/azure-functions/functions-create-first-function-bicep?tabs=CLI)

Start with quickstarts/microsoft.web/function-app-create-dynamic/main.bicep and compare its defaults with templates/common/infra/bicep/core/host/functions.bicep in the linked Azure Dev repository. Review the corresponding quickstart documentation and determine the supported runtime names and versions. Done means the template and documentation agree on Linux defaults, runtimes, and runtime-version guidance.

Written by the indexing model from the issue text.