error when removing a job type from jobConfig.yaml

[sbliven]

Summary

Scicat returns 400 errors for any query which would include a job not found in the current configuration.

Steps to Reproduce

1. Add a custom job type in jobConfig.yaml, eg 'test_job'
2. Create a job of this type
3. Remove the job type from jobConfig.yaml & restart the backend
4. GET /api/v4/jobs

Current Behaviour

Currently this returns a 400 error:

{
  "status": 400,
  "message": "Invalid job type: test_job"
}

This is because scicat needs to check that the user has read access to that job, which requires knowing the job type's auth setting.

Expected Behaviour

I suggest that jobs with unknown job types be considered to have #admin authorization.

Details

[sbliven]

The easy work-around to this issue is to just delete the invalid jobs from the database when you change your jobConfig.yaml.