0xmovses/aptos event monitoring

[0xmovses]

Summary

Implements Stream for MovementCounterpartyMonitoring. We cannot subscribe to a ws on aptos-core because this functionality is not provided out-of-the-box, additionally the indexer only streams transactions no events. So we must query the rest end point directly.

MovementCounterpartyMonitoring must be Stream in order for the BridgeService to correctly operate, this is exemplified in the shared/tests code, it is also a trait bound.

Changelog

• Implements Stream for MovementCounterpartyMonitoring
• Uses `try_stream!
• Updates move module to correctly capture all the events in a struct and query by field. (I borrowed this pattern from the aptos governance module)

Testing

More top-level code needs to be added before I can integrate test this. In an attempt to keep the PR small. Will add that in a separate PR.

[Primata]

Here it's polling the first page, unlimited. Taking a look at the aptos method,

async fn get_bcs_with_page(
        &self,
        url: Url,
        start: Option<u64>,
        limit: Option<u16>,
    ) -> AptosResult<Response<bytes::Bytes>> {
        let mut request = self.inner.get(url).header(ACCEPT, BCS);
        if let Some(start) = start {
            request = request.query(&[("start", start)])
        }

        if let Some(limit) = limit {
            request = request.query(&[("limit", limit)])
        }

        let response = request.send().await?;
        self.check_and_parse_bcs_response(response).await
    }
    ```
not sure if pagination is being handled correctly as you'd want to use the previous start as the limit. 🤔 

[0xmovses]

Yes, good point. I can only meaningfully tweak this once I have the integration test so I can see what behaviour its giving me. I can try here but I'd be flying blind. But I have an idea for how to handle pagination within the Stream

[Primata]

Seems like process_response could be process_responses instead and return a tuple of locked_Events, completed_eventes and cancelled_events

[andygolay]

LGTM, pending completion of the outstanding todos and integration testing

[andygolay]

Perhaps it would make sense to list the todos in the Outstanding Issues section of the PR?

[0xmovses]

closing as all these changes are in #399