[Task (Infrastructure)]: Return IndexerError instead of anyhow::Error from Checkpoint handler in iota-indexer

[tomxey]

Description

Created based on #1701 (comment)

The main change would be to change error type in the Handler trait

iota/crates/iota-indexer/src/framework/interface.rs

Line 12 in 9ffa886

async fn process_checkpoint(&mut self, checkpoint: &CheckpointData) -> Result<()> {

from anyhow::Error to IndexerError and then refactor the rest of the code accordingly.

Consider making use of the new error variant IndexerError::CheckpointProcessingError introduced in #1701

[sergiupopescu199]

@iotaledger/l1-core-infra

After the re-fork the Handler trait does not longer exist and now the Worker trait from iota-data-ingestion-core crate is replacing the logic, the general issue is that iota-data-ingestion-core does not have a dedicated Error type but use anyhow which is not ideal as it is a crate not an application, I suppose we could create a new issue and close this one as it could include more changes than anticipated because the Worker trait is implemented in the following crates:

1. iota-analytics-indexer
2. iota-data-ingestion
3. iota-indexer-builder
4. iota-indexer

[kodemartin]

@iotaledger/l1-core-infra

After the re-fork the Handler trait does not longer exist and now the Worker trait from iota-data-ingestion-core crate is replacing the logic, the general issue is that iota-data-ingestion-core does not have a dedicated Error type but use anyhow which is not ideas as it is a crate not an application, I suppose we could create a new issue and close this one as it could include more changes than anticipated because the Worker trait is implemented in the following crates:

1. `iota-analytics-indexer`

2. `iota-data-ingestion`

3. `iota-indexer-builder`

4. `iota-indexer`

I agree @sergiupopescu199 let's plan a refactoring of iota-data-ingestion-core to use a library specific Error type through a new issue.