Feat/workflow list enhancement

[tdari]

This PR will enhance the workflow list by adding checkboxes to control workflows and changing the UI for this new feature.

• Implement Force stop run of a workflow #298
• Add action buttons for batch operations.
  Add a control for the disabled state of the action buttons.
• Update the alignment and density of rows.
• Add stop action endpoint for single workflow.
• Add REST endpoints for batch operations.
  • batch delete
  • batch run
  • batch stop
• Add the last run status of tasks to the workflow list.
• Add a single run button.
• Update the toast notifications for batch operations.
• Add unit tests for the new REST endpoints.
• Allow only a single run for a workflow to be running. (no reason to run the same workflow with the same params in parallel)

Current UI (WIP):

[luiztauffer]

@tdari this is looking neat, I like compact!

we are missing the "visualize workflow" action, though. Or, in your proposed design, how does the user navigate to the specific workflow visualization page?

[tdari]

hi, @luiztauffer. Individual list items are still redirecting to the details page. It's working as it was before.

[tdari]

@vinicvaz why do we have this restriction here in workflow_service.py? Is it something with Airflow? I think we should allow this to enable users to test their workflows. What do you think?

def run_workflow(self, workflow_id: int):
        .
        .

        # Check if start date is in the past
        if workflow.start_date and workflow.start_date > datetime.now(tz=timezone.utc):
            raise ForbiddenException('Workflow start date is in the future. Can not run it now.')

        if workflow.end_date and workflow.end_date < datetime.now(tz=timezone.utc):
            raise ForbiddenException('You cannot run workflows that have ended.')

        .
        .

[vinicvaz]

@vinicvaz why do we have this restriction here in workflow_service.py? Is it something with Airflow? I think we should allow this to enable users to test their workflows. What do you think?

def run_workflow(self, workflow_id: int):
        .
        .

        # Check if start date is in the past
        if workflow.start_date and workflow.start_date > datetime.now(tz=timezone.utc):
            raise ForbiddenException('Workflow start date is in the future. Can not run it now.')

        if workflow.end_date and workflow.end_date < datetime.now(tz=timezone.utc):
            raise ForbiddenException('You cannot run workflows that have ended.')

        .
        .

Hey @tdari .

In Airflow, if a DAG has a start date set in the future, triggering a run will only schedule it for execution after the start date, transitioning the DAG to a 'scheduled' state instead of running it immediately. That is why we are blocking this operation for workflows with start date in the future.

[tdari]

I see thanks @vinicvaz

[tdari]

I've finished most of this PR. Can you test it before I start writing tests? There may be some mistakes I haven't noticed, and I've had to decide on naming conventions, endpoints, etc. Let me know if you have a better proposal. I couldn't separate commits as I expected. Sorry for such a big change list.