✨ [Job Engine] Added JobDataCleanupJobEndCallback to delete JobInstanceData after JobExecution has ended

[Coduz]

This PR adds a JobDataCleanupJobEndCallback to remove data of the JobInstance after the JobExecution has run.

This will avoid the jbtc_* tables to group up in size and row count making some operations being slow (eg: checking if a Job is running when is has a lot of Execution.

Related Issue
None

Description of the solution adopted
Leverage the IJobEndCallbackService to extend the default JobEndCallbackManagerImpl and register a custom JobEndCallback that deletes data

Screenshots
None

Any side note on the changes made
Perhaps, also the check for queued job should be moved to a JobEndCallback. Unfortunately only parameter given to the JobEndCallback is the jBatch jobExecutionId, which makes difficult to check which is the actual Kapua JobExecution that was running and start enqueued Jobs

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 16.76%. Comparing base (38c4367) to head (0335034).
Report is 3 commits behind head on develop.

Additional details and impacted files

@@              Coverage Diff              @@
##             develop    #4150      +/-   ##
=============================================
- Coverage      16.79%   16.76%   -0.03%     
  Complexity        22       22              
=============================================
  Files           2037     2037              
  Lines          52835    52835              
  Branches        4441     4441              
=============================================
- Hits            8874     8860      -14     
- Misses         43560    43572      +12     
- Partials         401      403       +2     

see 3 files with indirect coverage changes