[DO NOT MERGE] Some initial work on creating Debian Package

[AndrewQuijano]

Your checklist for this pull request

• [ ] I've documented or updated the documentation of every API function and struct this PR changes.
• [X] I've added tests that prove my fix is effective or that my feature works (if possible)

This is updating the CI, so every release, this would be tested.

Detailed description

A new (in progress) feature is made such that every time a new release is created, a Debian package is created and uploaded to releases.

Approach: Create a Debian folder, this contains everything needed to create a Debian package. How this works is it creates a docker container where capstone is compiled and a Debian package is created. The CI is updated to run the script which creates the container for upload release.

Also, I updated the release process to not use end of life uploading. See the link, I updated the CI to reflect this too https://github.com/actions/upload-release-asset

Current Issue:

Based on my hack in the Dockerfile, it seems to identify which files I need to copy in the Debian package

...

Test plan

This still technically needs a bit more work, if you can please help finish this. But essentially how you know this works is when you create a release, this will create a temporary docker image to create a Debian package which is uploaded to the release. I based my work on what the PANDA team did here

I would suggest once the stage happens that the Debian package is created, see if you can use apt-get install with the package and capstone works as expected.

https://github.com/panda-re/panda/tree/dev/panda/debian ...

Closing issues

closes #2398 ...