Accept number equal to 1 or 0 while checking data type of bool.

[jlamarr22]

Change Description

Change:
For the validation of data type of bool during serialization, additionally accept number which equal to 1 or 0. Closing #624 in favor of this PR due to adding tests and switching base branch to develop.

Reason of the change:
You could see there is a buffer.push(data ? 1 : 0); just below the changed line. It converts all boolean value to 1 or 0.
Hence, if we fetch the payload in an action which is pushed by eosjs before, all boolean fields would become 1 or 0. If we repeat the same payload with the field using value of 1 or 0, it will be invalidated during the check because the check only accept boolean as the data type.

In our latest eosio-explorer required feature, there is a repeat push action feature which depends on the last fetched payload and it will be blocked by the check ( not accepting 1 or 0 ). We need this change in eosjs for us to finish the feature.

API Changes

• API Changes

Documentation Additions

• Documentation Additions

[tbfleming]

Note that the "Reason of the change", copied from #624 is nonsensical. The real reason is nodeos's abi_serializer produces 1 and 0 for booleans.