Migration to wireshark 4.4.x [3/3]

[amitrahman1026]

From the perspective of the user, using this crate for the first time, should generate bindings.rs for their specific set up. They should not have to worry about getting their example plugins to compile. Also side note, wsdf should be called a plugin framework to be a little more accurate its utility.

Summary of changes

In terms of efficiency, it is reasonable to have pre generated bindings. However, this reduces portability and we should move to stop remove tracking for bindings.rs in this crate.

For ease of use, the first time cargo build is run, a fresh generation of bindings will be run, and user can continue to regenerate bindings.rs in subsequent build if they wish to with cargo --features bindgen

Portability scripts have added that will provide users a base to port wsdf generated plugins on macOS system as well.

Up next

• Rebase in Jun Yi's big refactor
• Remove tracking on bindings.rs
• Integration testing hooks to ensure parity in generated plugins
• Find a better solution to find system libwireshark and other dependencies, and about building wireshark from source. Scope of this crate should be aimed at providing plugin generation for system's existing wireshark
• In light of that, I am considering restricting declaration of version type if we are trying to link against system install of wireshark because it can lead to incompatibility