fix upper_bound bug in chain_plugin; update cleos to use fixed upper_bound correctly

[arhag]

See the comment here: #6070 (comment)

Change get_table_rows_ex to set upper (within the if statement checking if upper_bound was specified by the caller) using the upper_bound function rather than the lower_bound function.

Change get_table_rows_by_seckey to set upper (within the if statement checking if upper_bound was specified by the caller) using the upper_bound function rather than the lower_bound function. However the upper_bound function should be passed a tuple that includes a third argument std::numeric_limits<uint64_t>::max().

Change get_table_by_scope to set upper (within the if statement branch that asserts that upper_bound was specified by the caller) using the upper_bound function rather than the lower_bound function and with a tuple boost::make_tuple(p.code, scope, std::numeric_limits<uint64_t>::max()) passed to the upper_bound function.

Set lower_bound_lookup_tuple and upper_bound_lookup_tuple appropriately based on passed in RPC arguments. Ensure lower_bound_lookup_tuple <= upper_bound_lookup_tuple. Then the lower and upper iterators in all cases should just be:

auto lower = idx.lower_bound( lower_bound_lookup_tuple );
auto upper = idx.upper_bound( upper_bound_lookup_tuple );

Audit all uses of lower_bound and upper_bound in cleos and update them as appropriate to work with the corrected upper_bound implementation in chain_plugin.

[arhag]

Resolved by #6285.