Updates in database_api patterns related to fixes in ordering by time

Some patterns had to be generated with find_comments as differences in cashout_time make it impossible to match with previous results (should be ok after HF17). Also fat node used wrong index in case of list_comments with by_author_last_update (used the same as with by_last_update despite proper index existing). New HiveMind uses proper order but results are incomparable with old fat node.

On top of differences in newly comparable patterns that were of the same kind as before, we've started accepting more:

• children_abs_rshares - now always 0; before HF17 it was used to calculate cashout time, now the value is still collected but for nought
• reward_weight - now always 10000; between HF12 and HF17 "spamming" top posts would result in them having rewards lowered - no longer relevant and we have no source of valid value
• net_rshares - now always 0 after final payout; negative values used to stay forever even after final payout but since cashout object are removed after HF19 database_api from hived would be returning 0 after payout, so we do the same for consistency