Adapt behaviour of KeptnAppCreationRequest controller during corner cases processing

[odubajDT]

Part of #514

Pre-requisites :

• Bootstrap KeptnAppCreationRequest #612
• Implement logic for KeptnAppCreationRequest controller #613

Goal

Implement the controller logic to handle KeptnAppCreationRequest resources in corner cases of automatic discovery of the application.

Technical Details

Implementation of Reconcile() function of KeptnAppCreationRequest controller

Definition of behavior in corner cases:
What happens if you apply a KeptnWorkload with v1 and before the timeout also with a v2? What happens if v2 is applied after the timeout?

• KeptnWorkload v2 applied before the timeout expired: Each of the currently present workloads will be added to the app. If there are multiple versions of the same Workload, the latest applied (by time) one will be added.
• KeptnWorkload v2 applied after the timeout expired: A change in the version of a Workload could be interpreted as a change in the overall KeptnApp. In this case a change of KeptnApp will result that a new KeptnAppVersion with a newly computed version will be created. Noteworthy: Currently, Only the new workload will be displayed in OTel trace of new KeptnAppVersion version, all other workloads will, if unchanged be still be part of the previous KeptnAppVersion version.

Acceptance Criteria

• KeptnAppCreationRequest controller covers corner cases

DoD

• Implemented controller logic according to the description of corner cases
• Unit tests
• Component tests
• Kuttl tests

Note

PoC of implementation available here: #559