* clean up configuration parameters
* use dynamic max_inline_action_size configuration parameter to limit size of inline actions
* use dynamic max_inline_action_depth to limit recursion depth of inline actions
* change deferred_trx_expiration_window parameter into a dynamic configuration parameter
* add numerator and denominator configuration parameters for later context free data discount implementation
* bill delayed transaction for the additional net usage of the eventual retirement of the deferred transaction

Since the delay has now moved into the authority, the delay tests were not setting the delay properly in the updateauth actions.
This meant that a delay was not enforced and the tests were not actually testing delays properly.

I fixed the tests to properly set the delays, but this means that additional tests in delay_tests now fail.
The additional tests that failed are: link_delay_permission_change_test, link_delay_permission_change_with_delay_heirarchy_test, link_delay_link_change_test, and link_delay_link_change_heirarchy_test.
The reason these fail is very likely due to off-by-one errors due to change of now() from head block time to pending block time.

In this commit, I fixed link_delay_permission_change_test but have not yet gotten to the other three tests.

Also, of the two delay tests that were originally failing, I fixed canceldelay_test but have not yet fixed canceldelay_test2.

The now() intrinsic was replaced with a current_time() intrinsic which returns the current time (not head block time) in microseconds since epoch.

A now() function was defined in eosiolib/system.h which returns current_time()/1000000 so that existing contracts which use now() need minimal changes.

The publication_time() intrinsic was modified to also return the time as microseconds since epoch.
The only contracts that used publication_time() so far were for tests and those tests have been updated to reflect the new meaning of publication_time() and current_time().

Also, it now checks to ensure the proposed producer schedule would actually change the schedule.

Also update native action handlers to reflect changes in PR #2440.

not working

Clang was actually generating the right code; compiler_builtins had the problem because the return value semantics of the Berkeley softfloat library are not the same as that of the compiler builtin intrinsics.

My fixes will work for now until we replace the compiler_builtins intrinsics altogether with the change described in #2487.

I fixed a bug in wasm_interface with long double compiler builtins. However, clang is generating bad wast code involving the long double comparison, so the tests still fail.

Test does not yet work because the long double functions were removed from the WASM-side standard library.

Also added print support for signed 128-bit integer.

Added test cases into print_tests to test printing int128_t, float, double, and long double.

Implement long double secondary index on native side and add support for long double in eosio::multi_index.

Also use double* in double C DB API, and use float64_t in double secondary index.

add back current_receiver intrinsic and use it to provide a quick fix to multi_index bug (until the better solution is implemented for RC2)

The multi_index bug was that attempts to use multi_index to create/modify/erase table rows of accounts other than the current receiver would not fail as it should and would instead likely unintentionally trample over data in the current receiver's tables.

Also, `execute_after` (or `delay_until`) parameter is removed from the `send_deferred` contract API since that can be specified using the `delay_sec` field in the transaction header.