[DEV-7573] Refactor rmqstream library

[RabidGhost]

Description

Refactor the rmqstream rust library. The main goal of the refactor is to bring the library to the 2024 edition, update the rust version to 1.93.1 (latest at time of writing), and update all dependencies to latest versions.

In addition to refactors, load_balancer_mode(true) has been enabled on the RabbitMQ producer. This is not strictly nessesary as stream hostname resolution has now been updated for namespaced hosting capacity service.

Tests have been for logging and tracing setup.

Update to the 2024 edition

In the 2024 editon, static mut is disallowed (an error lint by default). It is very tricky to reason about correctly. We have moved to using static and Mutexs.

Remove unused dependencies

• the futures crate was unused
• lazy_static functionality is now included in the standard library

Update to Rust 1.93.1

No issues in upgrading to the latest Rust version. Means all dependencies can go to latest without any issues.

Associated tasks

None

Test Steps

The changes have been tested on staging, and tests for logging have been added. Other tests should be part of the calling code, or the HCS integration tests.

Checklist

Code

• I have performed a self review of my own code (including checking issues raised when creating the PR).
• I have added/updated unit tests for these changes, and if not I have explained why they are not necessary.
• I have commented my code in any hard-to-understand or hacky areas.
• I have handled all new warnings generated by the compiler or IDE.
• I have rebased onto the target branch (usually main).

Security

When developing applications, use following guidelines for information security considerations:

• Access to applications should be protected with security keys/tokens or usernames and passwords;
• All sessions are encrypted if possible;
• All application input is sanitised before being acted on (ie SQL statements, etc);
• Log messages, and especially client-facing ones, must be handled securely and must not leak credentials information (internal URLs, passwords, tokens).

• I have considered if this change impacts information security and made sure those impacts are handled.

Documentation

• I have updated the changelog.
  • Fixes to unrealeased change?
• I have updated any documentation required for these changes.
  • No changes to public API

Breaking Changes

• I have considered if this is a breaking change and will communicate it with other team members by posting it on the Slack breaking-changes channel.

None