This makes BOLT_ENABLE_RUNTIME a user-configurable option. It defaults (almost) the same as the current behaviour, but allows one to explicitly disable the runtime.
- It adds a check for Linux or Darwin, AFAICT those are the only two hosts the runtime supports. So don't default on if not on those hosts.
- If the runtime is enabled, it adds a check that /proc/self/map_files is readable. The RHEL7 VM dev machine I have is configured such that it is not, and consequently the runtime fails. The failure mode is that one can open() the dir, but getdents fails with EPERM. This is apparently not too uncommon.