Brooks Townsend

Rebased this PR off of `main` and added a component example so folks can see this in action. With `reqwest` it is really nice looking

Thanks @pimeys ! I'll have to take a look at your implementation. I was honestly considering making the component implementation blocking/sync for now, since `wasi-http` doesn't have any native async....

@pimeys do you have an example component that you used with these changes?

> The wit definitions do have async versions of the needed apis. Yep! You're correct, all I meant to say was that currently functions that you can export with components...

@pimeys curious if you have any recommendations for https://github.com/seanmonstar/reqwest/pull/2290/commits/33aa9d76484826a5069ff83adbc33f96fa5ea239, I've pulled in your changes but unfortunately for the component included I wasn't able to actually use the async support you...

Closing in favor of #2453. Will keep my fork+branch alive in case this PR is useful for reference in the future.

reverting to draft, try running this command for validation: ``` cargo test --workspace --all-targets --all-features ```

Ooh @jamesstocktonj1 this is a really cool feature idea! I don't think this would be all that difficult to implement in the spreadscalers + daemonscalers, and we might be able...

@Aditya1404Sal interesting... just to be sure, what are you testing with? Is it an HTTP app? I would recommend updating to 0.22.0, because there was a bug with that future...

@Aditya1404Sal anywhere in that component adding a time.sleep should be enough, if it's not then it might be an indicator that the future isn't able to stop the execution of...