Manage backups for VCIO

[TG1999]

Right now prod i.e (public.vulnerablecode.io) has both V1 and V2 instance running on it, which takes a lot's of disk space very frequently, we need to define a backup management policy and V1 and V2 segregation policy so the space does not run out quickly.

Some suggestions that we can work on

• Seperate V1 and V2 on different machines and support V1 till EOL (30th June 2026)
• Write a pipeline that import data from https://github.com/aboutcode-data/security-advisories
• backup only for the tables like API users, staff users etc

[TG1999]

Long term solution post we retire V1

Decouple importer and improver process from web services. We might use federatedcode as a place where we publish our data through import and improvers. Then web services machine will import those published advisories and will use DB to serve requests.