Decide on binary release strategy

With some help from some great contributors, we are (finally) arriving at a platform independent built strategy (See #232). This brings us towards the next big question, which binaries should the J2V8 project provide? We have several options:

1. Android (Arm, x86, x64, Arm64) with and without node support*
2. Linux (x64 and x32) likely with node support
3. Windows (x64 and x32) likely with node support
4. Mac x64 with node support
5. An All-In-One with all platforms for easy deployment
6. Node versions (we currently support 7.4, but some want 7.10)
7. Stripped and non-stripped symbols for some / all platforms (this reduces the size, but makes debugging harder)
8. Other configurations?

* Node.js support add several MB to the final build, so we may not want it in all Android archives

I won't be able to support all these platforms myself, but maybe we can find a way of crowd sourcing this, so those interested in certain configurations can handle the publishing of them. I would like the publishing to be as easy as possible, and if those who are actually using the builds are responsible for publishing them, then we can be sure that the QA will be addressed.

Does anyone have thoughts on this?