Fix normalization not lowercasing sender/receiver

[cor]

Some examples:
D990d551792d22996a1E0b5637008F2e9A6C3882

this is blocking #2711

[KaiserKarel]

I've lowered this in v0.transfers now @qlp, which resolves the immediate issue but won't be super friendly to indexes etc.

[KaiserKarel]

Should adjust this in v0.transfers_view such that we store them lowered.

[qlp]

@KaiserKarel I've fixed all duplicate key issues in push tables and reverted you 'lower' patch.

results are the same:

select * from (
             SELECT transfers_push.sender,
       transfers_push.receiver,
       lower(transfers_push.normalized_sender)   AS normalized_sender_lower,
       transfers_push.normalized_sender,
       lower(transfers_push.normalized_receiver) AS normalized_receiver_lower,
       transfers_push.normalized_receiver,
       transfers_push.source_transaction_hash,
       transfers_push.source_transaction_index,
       transfers_push.source_timestamp
FROM transfers_push) t
         where t.normalized_receiver_lower <> t.normalized_receiver or
               t.normalized_sender_lower <> t.normalized_sender
 order by t.source_timestamp desc
limit 500

results in just 15 rows (all a result of non-delete records after block reorgs). I'll create a new item to fix that