Decoupling Message Generator and Deprecating Serde Variant in Binary_SV2

[Shourya742]

Currently, we maintain two variants of binary_sv2: the serde variant and the no-serde variant. The serde variant was originally retained to support the Message Generator. However, since we are now working to decouple the Message Generator into a separate repository, maintaining the serde variant of binary_sv2 is no longer necessary. This issue will serve as a tracker for all required changes to complete the migration and deprecate the serde variant.

Action Items:

1. Decouple the Message Generator: Move the Message Generator to its own repository. The new repository will depend on protocol crates that reference a previously released version of the protocol where serde was still supported as a feature flag. This task is currently led by @plebhash, and the ongoing development can be tracked here: [GitHub Repository - Stratum Message Generator](https://github.com/stratum-mining/stratum-message-generator).

2. Deprecate the serde variant of binary_sv2: Designate the no-serde variant as the primary and sole variant of binary_sv2. Additionally, remove all with_serde feature flags throughout the roles and protocol.

3. Refining the current MG Test workflow to checkout the MG from its future repo

Both task 1 and 2 are disjoint, and share no dependence.

• Point crates in Message Generator to point at crates.io and not relative workspace path. #1421

[jbesraa]

for (2) we should include roles workspace as well

[plebhash]

it's also important to highlight that (1) is not a pre-requisite for (2).

[GitGab19]

We should also add another point in this list which is:

• refining the current MG Test workflow to checkout the MG from its future repo

In this way we could move it out and still run those tests in our CI, while migrating every test.