Update database trigger to honour a new feature flag to turn it off

Why are we doing this work

To be able to safely test this change, we need to be able to deactivate the database trigger and the application level code we're replacing it with interchangeably. This requires us to devise a method with which we can prevent the trigger from running with while we test the new application code.

Relevant links

Non-functional requirements

• Documentation:
• Feature flag:
• Performance:
• Testing:

Implementation plan

• Modify the database trigger to respect a feature flag such that we can prevent it from working on demand, preferably with a namespace/project actor so that we can test it in a localized fashion on GitLab.com.

Verification steps

• Turning off vulnerability read creation will effectively make vulnerabilities invisible in the vulnerability report. If you switch the trigger off for a project, then ingest some vulnerabilities and can't see them in the vulnerability report, then it's worked.