MassTransit Alterations Dispatcher

[sfmskywalker]

This PR adds a MassTransit implementation for the alteration job dispatcher service. This allows the engine to scale out into multiple application containers to increase throughput and resiliency.

=== auto-pr-body ===

Summary
This pull request includes a set of changes and additions related to the MassTransit feature, implemented to allow running alteration jobs in the background. Changes include adding a FindManyIdsAsync method to IAlterationJobStore, refactoring fields such as AlterationPlan.Status and AlterationJob.Status to use strongly typed enums and configuring indexes on selected fields.

List of Changes:

• Added Elsa.Alterations.MassTransit project to solution file
• Added a ProjectReference for Elsa.Alterations.MassTransit in the Elsa.WorkflowServer.Web.csproj
• Adjusted the Sqlite connection string in the appsettings.json to point to the App_Data/elsa.sqlite.db
• Added RunAlterationJob message to Elsa.Alterations.MassTransit.Messages
• Added ResumeWorkflowInstance handler
• Added DispatchWorkflowRequestConsumer to Elsa.Alterations.MassTransit.Features
• Updated configurations for AlterationJobStore and AlterationPlan
• Added FindManyIdsAsync method to AlterationJobStore
• Added MassTransitAlterationsFeature, UseMassTransit and AddMassTransitConsumer methods to ModuleExtensions

Suggested Refactorings/Modifications:

• Replace hardcoded database names with constants in AlterationPlan and AlterationJob configurations
• Use strongly typed enums instead of strings to represent the AlterationPlan.Status and AlterationJob.Status fields
• Add documentation comments to the src/modules/Elsa.Alterations.Core/Contracts/IAlterationJobStore.cs to describe the changes
• Split the src/modules/Elsa.Alterations.Core/Services/DefaultAlterationJobRunner.cs code into smaller functions to improve readability
• Add unit or integration tests to validate the changes implemented in the pull request.