msft_proxy4: new wrap

[mochaaP]

microsoft/proxy#375

[bgilbert]

Thanks for submitting Meson support upstream. In WrapDB, though, wraps must point to upstream releases. This wrap not only points to an untagged commit hash, it's a commit in an unmerged PR, with no indication that upstream intends to actually merge it. That won't work: we need to be able to maintain the Meson config downstream in WrapDB until upstream takes responsibility for maintaining it as part of a release.

If the purpose of this PR is to test the code in WrapDB's CI, that's fine, but please mention that clearly in the PR and mark it as draft. Otherwise, you'll need to point the .wrap to the most recent official release and copy the Meson files into a patch_directory in the PR.

[mochaaP]

marking as draft until merged upstream.