[indexer-2] rework some indices (#14203)

## Description 

As realized GIN indices works poorly in our use case where order by
tx_sequence_number is highly desired. This PR makes the following
changes wrt schema/indices:
1. break down `tx_indices` table into individual tables `tx_seners`,
`tx_recipient`, `tx_input_objects`, `tx_changed_objects` and `tx_calls`.
Check their `up.sql` files for schema.
2. nuke the `sender` index on `events` table as it's GIN too (thanks to
@gegaowp for pointing out we don't need a new table `event_sender`
because `tx_senders` has what we what already.

Because the addition of new tables, there is some changes in parallel
commit in the ingestion path.

Also note that in several places I write raw queries (but no SQL
injection risk) for proof-of-concept purposes. If there is strong desire
to use diesel ORM, I will try to make it work, but it will take a bit of
time as i'm not fluent in diesel yet.


## Test Plan 

How did you test the new or updated feature?

---
If your changes are not user-facing and not a breaking change, you can
skip the following section. Otherwise, please indicate what changed, and
then add to the Release Notes section as highlighted during the release
process.

### Type of Change (Check all that apply)

- [ ] protocol change
- [ ] user-visible impact
- [ ] breaking change for a client SDKs
- [ ] breaking change for FNs (FN binary must upgrade)
- [ ] breaking change for validators or node operators (must upgrade
binaries)
- [ ] breaking change for on-chain data layout
- [ ] necessitate either a data wipe or data migration

### Release notes
1. break down `tx_indices` table into individual tables `tx_seners`,
`tx_recipient`, `tx_input_objects`, `tx_changed_objects` and `tx_calls`.
Check their `up.sql` files for schema.
2. nuke the `sender` index on `events` table as it's GIN too (thanks to
@gegaowp for pointing out we don't need a new table `event_sender`
because `tx_senders` has what we what already.

Author: longbowlu

crates/sui-indexer/migrations_v2/2023-08-19-044020_events/up.sql

@@ -18,7 +18,7 @@ CREATE TABLE events
     PRIMARY KEY(tx_sequence_number, event_sequence_number)
 );
 
-CREATE INDEX events_senders ON events USING GIN(senders);
-CREATE INDEX events_package_module ON events (package, module);
-CREATE INDEX events_event_type ON events (event_type);
+CREATE INDEX events_package ON events (package, tx_sequence_number, event_sequence_number);
+CREATE INDEX events_package_module ON events (package, module, tx_sequence_number, event_sequence_number);
+CREATE INDEX events_event_type ON events (event_type text_pattern_ops, tx_sequence_number, event_sequence_number);
 CREATE INDEX events_checkpoint_sequence_number ON events (checkpoint_sequence_number);

crates/sui-indexer/migrations_v2/2023-08-19-044035_tx_indices/up.sql

@@ -0,0 +1,2 @@
+-- This file should undo anything in `up.sql`
+DROP TABLE IF EXISTS tx_recipients;

crates/sui-indexer/migrations_v2/2023-10-06-204335_tx_recipients/down.sql

@@ -0,0 +1,7 @@
+-- Your SQL goes here
+CREATE TABLE tx_recipients (
+    tx_sequence_number          BIGINT       NOT NULL,
+    -- SuiAddress in bytes.
+    recipient                   BYTEA        NOT NULL,
+    PRIMARY KEY(recipient, tx_sequence_number)
+);

crates/sui-indexer/migrations_v2/2023-10-06-204335_tx_recipients/up.sql

@@ -1,2 +1,2 @@
 -- This file should undo anything in `up.sql`
-DROP TABLE IF EXISTS tx_indices;
+DROP TABLE IF EXISTS tx_senders;

crates/sui-indexer/migrations_v2/2023-08-19-044035_tx_indices/down.sql renamed to crates/sui-indexer/migrations_v2/2023-10-06-204340_tx_senders/down.sql

@@ -0,0 +1,7 @@
+-- Your SQL goes here
+CREATE TABLE tx_senders (
+    tx_sequence_number          BIGINT       NOT NULL,
+    -- SuiAddress in bytes.
+    sender                      BYTEA        NOT NULL,
+    PRIMARY KEY(sender, tx_sequence_number)
+);

crates/sui-indexer/migrations_v2/2023-10-06-204340_tx_senders/up.sql

@@ -0,0 +1,2 @@
+-- This file should undo anything in `up.sql`
+DROP TABLE IF EXISTS tx_input_objects;

crates/sui-indexer/migrations_v2/2023-10-06-204348_tx_input_objects/down.sql

@@ -0,0 +1,7 @@
+-- Your SQL goes here
+CREATE TABLE tx_input_objects (
+    tx_sequence_number          BIGINT       NOT NULL,
+    -- Object ID in bytes. 
+    object_id                   BYTEA        NOT NULL,
+    PRIMARY KEY(object_id, tx_sequence_number)
+);

crates/sui-indexer/migrations_v2/2023-10-06-204348_tx_input_objects/up.sql

@@ -0,0 +1,2 @@
+-- This file should undo anything in `up.sql`
+DROP TABLE IF EXISTS tx_changed_objects;

crates/sui-indexer/migrations_v2/2023-10-06-204352_tx_changed_objects/down.sql

@@ -0,0 +1,7 @@
+-- Your SQL goes here
+CREATE TABLE tx_changed_objects (
+    tx_sequence_number          BIGINT       NOT NULL,
+    -- Object Id in bytes.
+    object_id                   BYTEA        NOT NULL,
+    PRIMARY KEY(object_id, tx_sequence_number)
+);