Migration to wireshark 4.4.x [1/*]

[amitrahman1026]

Changes

1. CMake related issues:

• Described here and here.

• There is a cmake module that is unnecessary and frequently causes hard-to-debug issues during CMake's configure run

• Additionally, it uses the Python imp module, which was removed in Python 3.12 (importlib has replacement functions since Python 3.4, but we don't need this, since we expect our modules to be inside our source tree.)

• Alleviates some cross building issues because there isn't exactly a pinned version of wireshark in wsdf

2. Changes from @seffradev to fix deprecated glib integers to fixed width C99 integers that newer versions of wireshark use. Many thanks for the groundwork and direction!
3. Improvements to build.rs for epan-sys crate that will propogate CMake errors.
4. Some documentation improvements better reflecting what wsdf is.

Coming up next:

Will be subsequently tracking in Todo.txt. Note: there are still outstanding fixes to be done before generated dissector plugins from wsdf will be working for newer versions.

Create integration testing for wsdf generated plugins

    As of now, besides unit tests, theres not an end to end testing framework
    that will give a better outlook on parity of wsdf generated plugins and
    wireshark native plugin functionality.

    A good approach would be to either hook onto the test suite of wireshark.


Improve cross platform building and pin releases to wireshark versions

    There have been various issues of end users not being able to build, not
    being able to generate usable plugins. This is in part due to the building,
    in part due to api changes in plugin creation and unmanaged wireshark
    versions.

    We could really use some unification on the build system.

    1. The most pressing issue wrt to plugins would be related to supporting
    changes in plug in creation APIs since wireshark 4.2.x.

    2. Some of the API now uses C99 types instead of
    [GLib types](https://gitlab.com/wireshark/wireshark/-/issues/19116).
    Appropriate changes will need to be backported down to 4.2.x.

    On top of that, there should be a better way to decouple and allow for
    flexibility of the underlying wireshark system.