Fix to allow producing node with --enable-stale-production time to become the producting node before it decides to go from speculating to waiting. GH #4971

Log which peer gives unexpected length messages

Add the git "version string" to get_info

Gh#4836 signals

Port 1.1.4 to develop

Release 1.1.4

bump version to 1.1.4

Consolidated Security Fixes for 1.1.4

This allows a quicker understanding of which peer is misbehaving, allowing faster turnaround time to blocking bad peers.

Backport of `fix/asset_mult_and_div` onto `release/1.1.x`

- Various regression/unit tests
Co-authored-by: NKevin Heifner <heifner_k@ociweb.com>
Co-authored-by: NMatt Witherspoon <32485495+spoonincode@users.noreply.github.com>

Update asset.hpp

Update asset.hpp

update crypto.h to use const char*

remove producer-subjectivness from leeway

make scheduled transactions subjectively fail on tx_cpu_usage_exceeded

producer plugin was treating leeway cpu exceptions as subjective which in turn implies to the rest of the producer code that the block is exhausted.  However, this exception rarely clears in a fresh block (only on wall-clock wobble) so it is in-appropriate for the producer plugin to consider this "subjective"

Update README.md

in EOSIO/eos#5001 the ability to bill appropriate CPU time for `soft_fail` and `hard_fail` scheduled transaction was added.  However, this exposes an ambiguity in the block structure:  There is no way to represent the objective failure of a scheduled transaction due to this limit.  This is because the measurement is subjective and must be strictly less than or equal to this limit otherwise the _block_ is objectively bad.  As a result, producers will no longer include those scheduled transactions in their blocks, giving each producer a chance to execute it in under the limited time or to another objective failure case.

Previous versions of `nodeos` were producing 0 values for billed transaction time which did not resolve the ambgiuity but shifted the failure mode from the desired mode (transaction exceeded an objective maximum) to a different failure mode (transaction under the minimum billable time) allowing those blocks to validate correctly despite the mismatch.

resolves EOSIO/eos#5057

Add filter-out history config option

Merge 1.1.3 into develop

Version 1.1.3

bump version to 1.1.3