moved just-in-time transaction packing to `apply_context` instead of the intrinsic, added/renamed intrinsics to match precedence set by the action api, added entries in the appropriate eosiolib hpp file

removed the utility thread which was in charge of compiling as we were seeing locks under load and a sufficiently multithreaded version would likely need a more robust solution

@DAWN390, DAWN391, DAWN392 issues.  Added a few more of the test_api tests to api_tests.cpp and added memory_tests

Provide a more natural interface in apply_context and have wasm_interface provide the shim code to accommodate the contract API.

Fixed get_active_producers for c API passing buffer byte length and added returning the number of bytes written, so user knows how many bytes were populated.

There are a couple native methods callable from WASM where the methods expect a NULL terminated char array (a string). Validate that the string lives entirely within active pages before dispatching it. Otherwise native code could segv if given a non-null-terminated string on the end of active pages.

WASM globals are disparate from WASM linear memory. Similar to how we reset linear memory after each invocation, we need to reset globals as well.

Linear memory is optional in WASM. Protect against crashes when a WASM doesn't use it.

Previously, the WASM "start" function would be called once right after compilation. This was problematic for two reasons. 1) It was called during a period of time not expected (not during any context), and 2) if the user was expecting the start function to be called for initialization it would not be called after the memory had been reset on subsequent apply() calls -- that could be a surprise.

Now call the WASM "start" function before each init() and apply().

@DAWN-390 fixed issue with sbrk not clearing between actions, and added page resizing to cache checkin to ensure page size goes back to default

rename scopes to locks from the perspective of the contracts, add account to the locks in shards and then deal with all the problems that caused

removed scope from transaction
renamed scope on action to account
added scopes to shard
fixed up scheduling and tests
fixed up eosioc

#1024 Fix to allow at least block 936299 to be successfully added to a new node's chain, Also addresses a secondary issue involving blocks with messages that take very close to the max txn processing time, sometimes the deadline is exceeded which then causes a fork and there is no recovering

fixed bugs in error handling WRT database undo states, fixed bugs in contract-side parsing of deferred transactions, added published time and sender (if one exists) to the apply_context and wasm ABI

fixes the issues with the deferred transactions and inline messages, implement changes to the proxy and a test case

added tests for the WASM currency contract and fixed issues it exposed, refactored contract initialization as a require_recipient where the logic of init vs apply is now in the wasm_interface

restored db table objects, extracted scope,code,table triplet from tables into a table id, moved EOSIO tokens to use the same data model as wasm token contracts