Allow disabling task drafts with env var setting

[nolanpro]

Issue & Reproduction Steps

We anticipate some clients will not want to use the task drafts feature

Solution

• Allow disabling drafts by setting TASK_DRAFTS_ENABLED to false

How to Test

This CI instance has drafts disabled. Ensure drafts are not being saved or loaded

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-15349

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

ci:next
ci:TASK_DRAFTS_ENABLED=false

[gustavobascope]

Approved
The task list didn't dissapear after quick fill when the results are empty. I made the comparison between next-qa and the new branch
Screencast from 03-05-24 15:19:33.webm
The autosave options doesn't appear when the env var is false

[processmaker-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
52.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube