Add WASM support to Azure function

#### What problem would the feature you're requesting solve? Please describe.
Like we have many kinds of work loads that we can run like isolated process, container , please add WASM also one of the workload that can be run in Azure functions

#### Describe the solution you'd like

1. When deploying the code, provide an attribute that will tell that the code has to be converted to wasm
2. Run the wasm in azure function.
This is to reduce the time for cold starts
#### Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
1. Support [Fermyon Spin](https://github.com/fermyon/spin) in azure functions
2. Like we are building exe and dll using dotnet publish and we have dotnet publish container, we need dotnet publish wasm, Then push wasm to Azure function

No files, tests, or entry points are named in the issue. Start by locating the Azure Functions host’s deployment and worker/runtime entry points, then compare the requested deployment attribute and WASM execution path with the Fermyon Spin and dotnet publish alternatives. Done means a defined deployment path can run WASM workloads in Azure Functions and addresses the stated cold-start goal.

Written by the indexing model from the issue text.