No restart of JOC Cockpit should be required on cleanup of Controller journals

Current Situation

• In case the journal files of the Controller are dropped and you have cluster agents in your environment having atleast one workflow with Cycle instruction then the restart of JOC Cockpit is necessary otherwise on deploying/releasing the Workflows/Schedules JOC Cockpit throws the below error:

  2024-05-21T14:35:36,687 INFO  JControllerProxy-35  c.s.j.c.ProblemHelper                        - 
  
  REQUEST: ./inventory/deployment/deploy
  
  PARAMS: {"controllerIds":["controller"],"store":{"draftConfigurations":[{"configuration":{"path":"/","objectType":"FOLDER","recursive":true}}],"deployConfigurations":[{"configuration":{"path":"/","objectType":"FOLDER","recursive":true}}]},"auditLog":{},"addOrdersDateFrom":"now"}
  
  USER: root
  
  2024-05-21T14:35:36,687 ERROR JControllerProxy-35  c.s.j.c.ProblemHelper                        - BadRequestError: MissingReferencedItem: Item 'Workflow:Test_WORKFLOW~4e660c44-e45b-4395-8bac-237e635a1c04' requires the missing 'Calendar:dailyPlan';
  
  MissingReferencedItem: Item 'Workflow:Test_WORKFLOW~4e660c44-e45b-4395-8bac-237e635a1c04' requires the missing 'Calendar:dailyPlan';
  
  MissingReferencedItem: Item 'Workflow:Test_WORKFLOW~4e660c44-e45b-4395-8bac-237e635a1c04' requires the missing 'Calendar:dailyPlan';
  

Desired Behavior

• The restart of JOC Cockpit should not be required if user deletes the Controller journal files.