feature: import official webview rust binding

[wusyong]

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• New Binding Issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes. Issue #___
• No

The PR fulfills these requirements:

• It's submitted to the dev branch and not the latest branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

[nothingismagick]

🎉 🔥 🚀 💯

[wusyong]

I could only verify the rust part, but it's good to merge imho. After this, I think we could open some refactor issues like Content type conversion, __initialized bindings and maybe others.

[lucasfernog]

I think binding functions (and maybe exposing that API to users) is going to have to wait, because Edge reloads the app and the window[name] bindings are gone. (I had to manually set the INVOKE binding every time on JS, but it's just a workaround; talked about it on the webview Discord channel and I might open an issue).

But if you think the Rust part is OK then LGTM

[lucasfernog]

@wusyong are you ok with the change file I've added?

[wusyong]

Of course! 😄