[REFACTOR] Improve WorkflowRequest Class

[joshpalis]

Is your feature request related to a problem?

Currently the Workflow Request class is used to handle several parameters such as provision, use_case, reprovision, etc, which is becoming unnecessarily complex and can lead to backwards compatibility issues with previous versions when serializing the requests.

What solution would you like?

Create subclasses of the WorkflowRequest class to handle each parameter

[boooby19]

Hello ! I am new to open-source projects. I am working as junior dev in c#/React, also have 3 year experience with Java. Can I work on this issue? Can you give me some more info? Thanks ! :)

[dbwiddis]

Hello over here too, @boooby19! I see you posted on #905 so let's get started on that one for your first commit(s) as this one is a bit more involved with the OpenSearch codebase serialization mechanism.

[junweid62]

I tried implementing the solution locally by creating subclasses of WorkflowRequest to handle parameters like provision, reprovision. However, I ran into some unavoidable issues in CreateWorkflowTransportAction. Since this class handles both create and update operations, it requires the same WorkflowRequest object for both cases. This dependency makes it challenging to separate the logic into distinct subclasses (e.g., CreateWorkflowRequest and UpdateWorkflowRequest) without extensive refactoring. If anyone has suggestions or alternative approaches, I’d love to hear them!