feat(matches): Implement Issue Matching ON creation of new component instances

[lolaapenna]

Split up into:

PoC scope + non-PoC scope.

PoC scope - run issue match algorithm when comp instances are created

• Creation of new comp instances for issue matching
• Creating default repository for new service

[drochow]

The actual work package is:

on the creation of a component instance, we perform the issue matching:

• It fetches the services ( through relation to it) and issue repositories (through component version) related to the component instance
• identifies the issue repositories with the highest priority
• fetches the issue variants for these repositories and the given issues
• creates an issueMatch for each of this issues(of the variants) for this component instance

[drochow]

@dorneanu

The intermediate implementation draft can be found here:

https://github.com/cloudoperators/heureka/blob/basic_matching/internal/app/issue_match/issue_match_handler_events.go#L93-L286

[dorneanu]

Ok, thanks. That helps a lot. I think in general we need better descriptions and maybe also acceptance criterias for the issues/tickets.

Tomorrow I'll have a look at the draft and improve accordingly.

[drochow]

better descriptions and maybe also acceptance criteria

I agree, but that is also an additional effort to take, but maybe it's worth it.