SCMOD-8730: Support expiry policies

[xbreizh]

https://portal.digitalsafe.net/browse/SCMOD-8730

[buildmachine-sou-jenkins2]

CI Build Link:
http://sou-jenkins2.swinfra.net:8080/job/JobService/job/JobService~job-service~SCMOD-8730~CI

[buildmachine-sou-jenkins2]

The Documentation QA site for this branch has been built:
https://pages.github.houston.softwaregrp.net/sepg-docs-qa/JobService_CI_job-service_SCMOD-8730

[xbreizh]

@dermot-hardy I think that I understand what you mean with the RFC 3339 but that would mean passing a date directly so the calculation would have to be made on client's end.
What I was thinking of was to make it easier on client's side and have them specify the date reference as a string then a number of days as integer and the calculation would be done whenever we run the checkExpiration job.
But I can go with a date if you prefer, Swagger uses RFC339 as default already
Here, I use the same object in and out (for newJob and job), but I could return an expirationDate instead for the job. I suppose that it would make more sense.
I tried having a default object to return but failed to find it so I am passing the different statuses and set a default for each element.

An example on json would be:

  "name": "Ingest documents submitted in batches A and B",
  "description": "This job ingests all of the documents that were in the A and B batches.",
  "expiration-policy": {
    "Active": {
      Policy:{
        "action": "delete",
        "referenceDate": "createDate",
        "duration": "70"
      }
    },
    "Failed": {
      Policy:{
        "action": "keep",
        "referenceDate": "lastUpdateDate",
        "duration": "7"
      }
    },
    "Completed": {
      Policy:{
        "action": "delete",
        "referenceDate": "lastUpdateDate",
        "duration": "7"
      }
    },
    "Waiting": {
      Policy:{
        "action": "delete",
        "referenceDate": "lastUpdateDate",
        "duration": "7"
      }
    },
    "Cancelled": {
      Policy:{
        "action": "delete",
        "referenceDate": "createDate",
        "duration": "7"
      }
    },
    "Paused": {
      Policy:{
        "action": "delete",
        "referenceDate": "lastUpdateDate",
        "duration": "7"
      }
    }  
  }, 
  "labels": {
    "repoId": "x37",
    "runNumber": "12",
    "workUnitId": "371"
  },
  "type": "batch-ingestion-job",
  "parameters": {
    "batches": ["batch-a", "batch-b"],
    "operationMode": "EXTRACT",
    "grammarMap": {
      "pii": []
    },
    "extractMaxMatches": 100
  }
}```

for the whole policy setup. But using the default, we should be able to pass only:

```json{
  "name": "Ingest documents submitted in batches A and B",
  "description": "This job ingests all of the documents that were in the A and B batches.",
  "expiration-policy": {
    "Active": {
      Policy:{
        "action": "delete",
        "referenceDate": "createDate",
        "duration": "70"
      }
    },
    "Failed": {
      Policy:{
        "action": "keep",
        "referenceDate": "lastUpdateDate",
        "duration": "7"
      }
    }
  }, 
  "labels": {
    "repoId": "x37",
    "runNumber": "12",
    "workUnitId": "371"
  },
  "type": "batch-ingestion-job",
  "parameters": {
    "batches": ["batch-a", "batch-b"],
    "operationMode": "EXTRACT",
    "grammarMap": {
      "pii": []
    },
    "extractMaxMatches": 100
  }
}```

[xbreizh]

New Explain Analyse
Source 1
Source 2