Collect a list of potential problems for distributing Node.js SEA binaries to end users

[jviotti]

In progress list:

---

• Space efficiency: end users are sensitive to binaries being pretty big (we see this a lot with Electron)
• Binaries with inline JS code on them tend to get flagged by anti-viruses (apparently Electron does some byte code transformation of their internal JS because of this)
• Extracting and loading/executing shared libraries and/or other programs on the fly is problematic with AVs
• Node.js links to GLIBC. Depending on the official release configuration, building against too new GLIBC versions reduces Linux compatibility

[jviotti]

Ping @zcbenz in case you have some more insights. This topic came up on the OpenJS SEA mini-summit last weekend. See #32 (comment) for more details.