Replace google drive with microsoft defender for vacancy and job application malware scanning

[KyleMacPherson]

Trello card URL

Changes in this PR:

This PR removes the google drive antivirus flow for the hiring staff job publishing flow and the jobseeker job application flow. Instead we switch over to using microsoft defender for storage. The key difference is that the antivirus scanning is done async on azure. To account for this change, in the flows mentioned above we will allow users to continue through the wizard steps if the file has not been scanned and only block them from progressing if the file is flagged as malicious or the azure scan has errored. We will however stop them from actually publishing the job or submitting the application until the file has been scanned and tagged as safe. See below for more detailed information on each flow with screenshots.

Hiring staff uploaded application form

• allows hiring staff to upload application form and progress to review and publish page before file has been scanned or has been scanned and flagged as safe
• errors if uploaded application form has been scanned as unsafe

- blocks publishing of vacancy until file has been scanned - blocks publishing of vacancy if file has been scanned and either the scan errors or the file is flagged as unsafe and prompts user to delete the file and try again

Hiring staff additional documents

• allows hiring staff to upload additional documents and progress to review and publish page before file has been scanned or has been scanned and flagged as safe
• errors if additional document has been scanned as unsafe

- blocks publishing of vacancy until file has been scanned - blocks publishing of vacancy if file has been scanned and either the scan errors or the file is flagged as unsafe and prompts user to delete the file and try again

jobseeker uploaded job application

• allows user to upload a job application form and progress to the review and submit page before file has been scanned or has been scanned and flagged as safe
• errors if uploaded job application form has been scanned as unsafe

- blocks submission of job application until file has been scanned - blocks submission of job application if file has been scanned and either the scan errors or the file is flagged as unsafe and prompts user to delete the file and try again

jobseeker catholic application form

• allows user to upload a baptism certificate and progress to the review and submit page before file has been scanned or has been scanned and flagged as safe
• errors if uploaded baptism has been scanned as unsafe

- blocks submission of job application until file has been scanned - blocks submission of job application if file has been scanned and either the scan errors or the file is flagged as unsafe and prompts user to delete the file and try again

Screenshots of UI changes:

Before

After

Checklists:

Data & Schema Changes

If this PR modifies data structures or validations, check the following:

• Adds/removes model validations
• Adds/removes database fields
• Modifies Vacancy enumerables (phases, working patterns, job roles, key stages, etc.)

If any of the above options has changed then the author must check/resolve all of the following...

Integration Impact

Does this change affect any of these integrations?

• DfE Analytics platform
• Legacy imports mappings
• DWP Find a Job export mappings
• Publisher ATS API (may require mapping updates or API versioning)

User Experience & Data Integrity

Could this change impact:

• Existing subscription alerts (will legacy subscription search filters break?)
• Legacy vacancy copying (will copied vacancies fail new validations?)
• In-progress drafts for Vacancies or Job Applications

[github-actions]

Review app deployed to https://teaching-vacancies-review-pr-8643.test.teacherservices.cloud on AKS

[KyleMacPherson]

This is just to allow us to test with eicar.txt to simulate a malicious file and will be removed before deploying.

[KyleMacPherson]

This is just to allow us to test with eicar.txt to simulate a malicious file and will be removed before deploying.

[KyleMacPherson]

This is just to allow us to test with eicar.txt to simulate a malicious file and will be removed before deploying.