feat: Error handling improvements for pipelines and scheduler

[chandrasekharan-zipstack]

What

• Fixed incorrect error handling practice in pipelines / scheduler
• Fixed some log messages pushed to the FE
• Removed unused arg with_log in WF / pipeline execution
• Removed some dead code

Why

• Errors were caught and re-raised differently for pipelines
• Unused args / code could cause confusion

How

-

Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)

• Yes, since it involves removal of some dead code around scheduler related data - this might already be present in the DB for existing pipelines. To not cause a regression - I've not refactored the scheduler function that executes the pipelines so it should work with the existing data as well. Added TODOs to mark that its unused

Database Migrations

• No

Notes on Testing

• Tried running a workflow, executed a pipeline with Sync Now and also attempted to schedule it with a cron string and checked how failures were reported
• NOTE: Pipeline execution reports a success however it did fail in the BE - @athul-rs @muhammad-ali-e

Screenshots

1. Inactive pipeline error message shown correctly

2. Execution continues on failures too

Checklist

I have read and understood the [Contribution Guidelines]().

[athul-rs]

@chandrasekharan-zipstack Overall the PR LGTM. Left couple of comments for clarification.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
2 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud