Replace symcrypt-bindgen crate with a script

[Vaiz]

This PR introduces several significant changes to the project, focusing on replacing the symcrypt-bindgen crate with a script. The generated bindings remain unchanged, ensuring no modifications to the public API of symcrypt-sys.

New scripts:

• Added scripts/generate-bindings.ps1 to generate Rust bindings using bindgen for a specified target triple.
• Added scripts/generate-all-bindings.ps1 to generate Rust bindings for all supported target triples, including installation instructions and prerequisites.
• Added scripts/generate-bindings.sh as a helper script to set the PATH to cargo binaries and call generate-bindings.ps1.

[Vaiz]

@microsoft-github-policy-service agree company="Microsoft"

[nnmkhang]

unsafe extern "C" {

unsafe extern "C" causes issues for me when doing my tests. Sent a message offline.

error: extern block cannot be declared unsafe
--> symcrypt-sys\src\bindings\x86_64_pc_windows_msvc.rs:1929:1
|
1929 | unsafe extern "C" {
| ^^^^^^
|
= note: see issue #123743 <rust-lang/rust#123743> for more information

---

Refers to: symcrypt-sys/src/bindings/aarch64_pc_windows_msvc.rs:2894 in b57945b. [](commit_id = b57945b, deletion_comment = False)

[nnmkhang]

sudo apt install pwsh clang libclang-dev

sent a message offline

[nnmkhang]

$importRules

Is it possible to separate the allow list to a separate file? I think it would be easier to maintain rather than directly modifying the .ps1 script. Wondering your thoughts

[Vaiz]

unsafe extern "C" causes issues for me when doing my tests. Sent a message offline.

fixed by setting rust-version to 1.64.0