epic: patch

[MR2011]

Description

We want to track patches in Services. These patches will be stored in a database table with the following main fields:

• Service
• Image Version (Component Version)
• Timestamps

Additionally fields might be required.

Whenever a Service doesn't have any ComponentInstances using a ComponentVersion, the Autoclosing will create a patch accordingly.

Tasks

• Only ListPatches for API required (no mutations)
• Patches will be considered in Issue Counts
• Test case simulating the patch in a Service to a new ComponentVersion

[michalkrzyz]

e2e tests - API List patches,
database - prepare single scan with data, which will be processed by patching function, expect element to be added to list of patches.

[michalkrzyz]

Test Scenario:

• We have a Service that has some running ComponenInstances of a ComponentVersion
• simulate a patch:
  Scanner reports back that the ComponentInstances are not there anymore
• create a patch for ComponentVersion and Service