Removal of clearance_required field from job result structure

We removed the field clearance_required from the job result structure. This affects all job results on the /api/jobs/ endpoint.

The main reason for this is that this was kind of a legacy part of the initial database structure and seemed to be rarely used/needed by anyone. Adding to this, the info stored in this field (a simple boolean) can be quite easily derived from the field description_string (+ job title in some cases) with a few search keywords, to determine if a job ad lists a security clearance (or the ability to obtain one) as a requirement for a job. A filter parameter for this didn't exist before, it was only part of the result set.

In case you were utilizing this info before you might want to check out this tutorial as a starting point for doing it in your own backend: How to Determine if a Job Post Requires Security Clearance). It was basically our approach, nothing fancy.

This change was part of a recent database/backend refactoring and migration effort to keep things as lean and simple as possible.

Related Docs