fix(indexer): fix events query

[stringhandler]

Description

Fixes the GraphQL query getEventsForComponent.

Motivation and Context

Previously this would work the first time it's called, but fail in subsequent attempts. This is because one of the queries was missing columns in the sql.

How Has This Been Tested?

Run an indexer, and call getEventsForComponent via GraphQL

What process can a PR reviewer use to test or verify this change?

As above

Breaking Changes

• None
• Requires data directory to be deleted
• Other - Please specify

[github-actions]

Test Results (CI)

83 tests   - 404   82 ✅  - 405   1h 11m 20s ⏱️ - 48m 50s
17 suites  -  42    0 💤 ±  0 
 1 files    -   1    1 ❌ +  1 

For more details on these failures, see this check.

Results for commit c09633a. ± Comparison against base commit 3cfbf6e.

This pull request removes 404 tests.

Scenario: Claim and transfer confidential assets via wallet daemon: tests/features/wallet_daemon.feature:89:5
Scenario: Claim base layer burn funds with wallet daemon: tests/features/claim_burn.feature:6:3
Scenario: Claim validator fees: tests/features/claim_fees.feature:6:3
Scenario: Confidential transfer to unexisting account: tests/features/transfer.feature:163:3
Scenario: Counter template registration and invocation: tests/features/counter.feature:7:3
Scenario: Create account and transfer faucets via wallet daemon: tests/features/wallet_daemon.feature:7:5
Scenario: Create and mint account NFT: tests/features/wallet_daemon.feature:133:5
Scenario: Create resource and mint in one transaction: tests/features/nft.feature:73:3
Scenario: Double Claim base layer burn funds with wallet daemon. should fail: tests/features/claim_burn.feature:44:3
Scenario: Indexer GraphQL requests events over network substate indexing: tests/features/indexer.feature:118:3
…

♻️ This comment has been updated with latest results.