fix: add missing is_latest filter to network account query

[SantiagoPittella]

Fixes ntx-builder crash on node restart after a network transaction has been processed. After a network transaction updates a network account, restarting the node causes the ntx-builder to fail with:

ERROR account actor already exists for account: 0x...
Error: Component ntx-builder failed
Caused by: event channel closed

The select_all_network_account_ids query was missing an is_latest = true filter. Without filtering for is_latest, both historical and current rows were returned, causing duplicate account IDs to be sent to the ntx-builder, which then attempted to spawn multiple actors for the same account.

Added .filter(schema::accounts::is_latest.eq(true)) to ensure only the current state of each account is returned. I saw that this filter was removed in #1481 so I want to confirm with @drahnr if we should fix it in another way.

[bobbinth]

Looks good! Thank you! I left one comment inline to be tackled in a separate PR.

[bobbinth]

Not for this PR, but we should probably replace network_account_id_prefix with something like network_account_type.

[Mirko-von-Leipzig]

I'll check tomorrow, but the ntx does need to handle duplicate accounts in its event loop. This is because it's possible for the account info to arrive from the store and also as part of the mempool event.

However the store should only be sending unique network accounts.

[bobbinth]

I'll check tomorrow, but the ntx does need to handle duplicate accounts in its event loop. This is because it's possible for the account info to arrive from the store and also as part of the mempool event.

However the store should only be sending unique network accounts.

I think we should merge this regardless as it fixes the store-side issue. We may need to follow up with improved handling on the NTX builder side though.

[SantiagoPittella]

I will continue with this two other PRs then, one for the prefix removal and another for the duplication handling

[drahnr]

Thank you!