feat(analytics): consider expiring and locked outputs

[DaughterOfMars]

Description

This PR tracks expiring and locked outputs in the address balance analytics, so that when the milestone is eventually handled those amounts will properly be transferred or added to the appropriate address. Each output with an expiration or timelock will create a record in the maps.

However!! this has potentially serious performance implications, primarily due to the memory usage of these tracking structures, which have no bounds!.

Alternatives

Conceptually, the same process could be instead applied to the database using a tracking table, something like this:

#[derive(Serialize, Deserialize)]
struct Id {
  milestone_timestamp: MilestoneTimestamp,
  output_id: OutputId,
}

#[derive(Serialize, Deserialize)]
struct TrackingDocument {
  _id: Id,
  address: Address,
  expiration_return_address: Option<Address>,
  amount: TokenAmount,
}

The usage of this table would be much the same as the HashMaps in this PR, and we could instead pass in the records for the current milestone for each balance analytic call. Additionally, this would allow chronicle to update the owning address for records in OutputCollection and LedgerUpdateCollection per milestone, potentially dramatically improving the functionality and performance of the explorer endpoints.

Conclusion

Due to the performance concerns, I don't want to merge this PR as-is, but rather keep it as a proof-of-concept for now.