[1.1.0] Test: Use EOS mainnet chain values for integration tests

[heifner]

The prior max_transaction_cpu_usage of 475ms allowed for very long running speculative transactions. These could cause delays which, in some cases, would be long enough for a test to timeout. See #1151 for details.

To avoid other possible differences in tests and real-world, set all genesis values of integration tests to the current EOS mainnet values.

EOS Mainnet eosio global table values

https://eosauthority.com/account/eosio?network=eos&scope=eosio&table=global&limit=10&index_position=1&key_type=i64&reverse=0&mode=contract&sub=tables

max_block_net_usage	target_block_net_usage_pct	max_transaction_net_usage	base_per_transaction_net_usage	net_usage_leeway	context_free_discount_net_usage_num	context_free_discount_net_usage_den	max_block_cpu_usage	target_block_cpu_usage_pct	max_transaction_cpu_usage	min_transaction_cpu_usage	max_transaction_lifetime	deferred_trx_expiration_window	max_transaction_delay	max_inline_action_size	max_inline_action_depth	max_authority_depth
1048576	10000	524288	12	500	20	100	200000	10	150000	100	3600	600	3888000	524287	10	10

Resolves #1151

[linh2931]

Are those all EOS mainnet genesis values? Can you put a copy of current genesis configs in the PR description?

[heifner]

These are not EOS mainnet genesis values, they are current values. I'll add the current values to the description.

[ericpassmore]

Note:start
category: Tests
component: Internal
summary: To avoid other possible differences in tests and real-world, set all genesis values of integration tests to the current EOS mainnet values.
Note:end