feat: async http calls from component and bugfixes

[SachaMorard]

Checklist

• I have read the Contributor Guide
• I have read and agree to the Code of Conduct
• I have added a description of my changes and why I'd like them included in the section below

Description of Changes

This pull request introduces the implementation of data collection components using WebAssembly (Wasm) and enhances the payload processing logic. The changes are primarily focused on the src/proxy/compute/data_collection/components.rs file.

• Implemented the initialization of Wasm components for data collection.
• Added the send_data_collection function to handle data collection http calls asynchronously.
• Introduced the anonymize_ip function to anonymize client IP addresses.
• Defined the HostView struct to manage Wasm context and resources.
• Remove x-forwarded-for from the wit protocol, because it's not useful

Related Issues

no issue

[KokaKiwi]

I feel like the whole "data collection" code should be the one being put in an async task instead of all the small bits (HTTP requests, etc.) since it's literally a "side-effect"
But that would probably require a lot more refactoring (cf. comment about cleaning up the payload conversion code) which maybe should be done in a dedicated cleanup PR?

[KokaKiwi]

Oh also the formatting seems odd, as in: there's a lot of code reformatting being done in this PR despite the cargo fmt previously done in #80, is that something from RustRover doing its own formatting rules?

[SachaMorard]

Oh also the formatting seems odd, as in: there's a lot of code reformatting being done in this PR despite the cargo fmt previously done in #80, is that something from RustRover doing its own formatting rules?

I don't think so. I use cargo fmt manually to be sure the last pushed commit is correctly formatted

[KokaKiwi]

I don't think so. I use cargo fmt manually to be sure the last pushed commit is correctly formatted

Uh. Do you maybe have a custom rustfmt.toml config file? Or maybe a different Rust version?