update iop-vmaas-reposcan to use vex data

[pfreyburg]

Why are you introducing these changes? (Problem description, related links)

The VEX downloader was already implemented into foremanctl (#638). The VMAAS master’s image is able to load this data a proceed them. The goal of this PR is to enable this in foremanctl.

What are the changes introduced in this pull request?

• set quay.io/redhat-services-prod/insights-management-tenant/insights-vulnerability/vmaas:latest as vmaas-reposcan’s image,
• set these variables:
  • SYNC_CSAF: "yes",
  • CSAF_VEX_BASE_URL: "http://iop-core-gateway:9090/pub/iop/data/csaf/v2/vex/",
  • CSAF_VEX_INDEX_CSV_ENABLED: "no",
  • (other variables left unchanged).

How to test this pull request

Steps to reproduce:

• enable IoP using foremanctl,
• check the vmaas-reposcan container:
  • you can see in the logs CSAF data are loaded and processed,
  • you can check vmaas_db database for loaded CSAF data (table csaf_file etc).

Checklist

• Tests added/updated (if applicable)
• Documentation updated (if applicable)