[BUG] Elsa V3 - Distributed environment setup issues

Sorry this is more of a question than a bug ....

## Description
Trying to get Elsa V3 working in distributed environment setup ...

The hosting environment architecture i'm looking to setup is as follows:

1. Custom .Net 8 Combined Blazor App \ API Nodes
Primarily used to programatically run Elsa V3 workflows immediately (in same container host) or dispatch them to the workers (running as .Net 8 docker containers behind load balancer)

2. Worker Nodes
Runs Elsa server + Hangfire + Elsa Studio
Dispatched workflows should run here.

I have enabled and configured the following Elsa V3 modules\packages which aids distributed hosting:
- Elsa.MassTransit
- Elsa.MassTransit.RabbitMQ (and configured with my RabbitMQ broker, seems to be working fine as far as I can tell)
- Elsa.Caching.Distributed
- Elsa.Caching.Distributed.MassTransit (and configured ... seems to be working fine as far as i can tell)
- DistributedLock.Redis (and configured redis instance .. seems to be working fine as far as i can tell)

However I am having issues with the following Elsa module\package which i am not sure what it does but appears in the sample apps:
**- Elsa.Workflows.Runtime.Distributed**
The above Elsa V3 package is only available via beta\pre-release Elsa package feed and thus i could not get my app to build up on the build server because i don't have control over.

Can you kindly explain what the extension method from this package **runtime.UseDistributedRuntime()** actually enabled outside of the above configured packages? I am not sure how it aids a distributed hosting setup?

And as a follow up question:
Any reason why this specific package is still in beta \ pre-release and is not available via standard packages publishing pipeline?

For refs sake my projects are all referencing the Elsa V3 3.2.0 version packages.