create github actions for native plugin authors to build/release plugins tracking both stable and dev

[robert-yates]

Is this a general concept that needs to be documented or a specifi API?
General Concept: What is the workflow for building and submitting a binja c++ based plugin,
how to compile for all platforms, how to version and manage dependencies and linking etc.

There is already a good python plugin documentation:
https://github.com/Vector35/community-plugins

What concept or API needs more documentation?
N/A

Is this documentation related to a specifi API?
N/A

**Are there any known examples of people using this API/concept? **
N/A

[fuzyll]

This is related to #2238.

[psifertex]

Ultimately the problem here is larger than just documentation and I'm going to edit the title accordingly. There really isn't a good workflow right now for installing native plugins. The only way to do it now is to build yourself for the version you want and install manually.

What we'd like to do is to provide better facilities (along with documentation) by which third-parties can release native plugins that are available in the plugin manager.

There's a few related issues. The first, already tracked in #2238 is support for native plugins in the plugin manager.

The second, but arguably more important issue is helping plugin authors create releases for stable releases, dev releases, and across Linux, MacOS, and Windows. I'm going to adjust the title of this issue to track creating public GitHub actions that let authors more easily build plugins this way.

[cblichmann]

I'm late to this issue: Building native plugins like BinExport using your build infrastructure or via a GitHub action, while obviously possible, will result in binaries without any code signatures. I'd still like to sign BinExport with the Google code-signining key, but that requires that we build internally (and that is not just a big corp being difficult :-)). So a GitHub action is useful in the general case, but will not help BinExport, unfortunately.