refactor: aggregate ravs depending on allocation type

[gusinacio]

• Create NetworkVersion trait used to define what kind of allocation we are handling.
• Add Generic for TapContext over NetworkVersion.
• Add Legacy and Horizon that implement NetworkVersion
• Wrap allocation Id address with new AllocationId enum.
• Create TapManager version depending on the allocation id variant.
• Implement aggregation within NetworkVersion trait.
• Add aggregator_v2 connection for SenderAccount.

TODO for future PRs:

• Implement all unimplemented traits for database queries.
• Test more extensively different types of allocations running.

Note

tap-agent is not well organized and we have a few files with 1k+ lines. Suggestions on how to organize are accepted.

[github-actions]

Pull Request Test Coverage Report for Build 13145110259

Details

• 155 of 239 (64.85%) changed or added relevant lines in 7 files are covered.
• 15 unchanged lines in 3 files lost coverage.
• Overall coverage decreased (-0.7%) to 77.999%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
crates/tap-agent/src/agent/sender_allocation.rs	31	32	96.88%
crates/tap-agent/src/tap/context/rav.rs	0	6	0.0%
crates/tap-agent/src/tap/context/receipt.rs	12	18	66.67%
crates/tap-agent/src/tap/context.rs	19	49	38.78%
crates/tap-agent/src/agent/sender_account.rs	56	97	57.73%

Files with Coverage Reduction	New Missed Lines	%
crates/service/src/tap/checks/deny_list_check.rs	2	94.4%
crates/watcher/src/lib.rs	4	92.71%
crates/tap-agent/src/agent/sender_account.rs	9	77.41%

Totals
Change from base Build 13141469414:	-0.7%
Covered Lines:	7158
Relevant Lines:	9177

---

💛 - Coveralls

[suchapalaver]

@gusinacio Thanks so much this looks great and thank you for all the amazing knowledge-sharing in the docs and comments! Just a couple of small things I caught and then good to go 🚀 !

[suchapalaver]

Awesome! 🙏