feat: Security must be a local file, not from repository

[c-pius]

Description

Changes proposed in this pull request:

• security config read from local file, not from git
• extended e2e tests to ensure multiple protecode entries are considered

Related issue(s)

• closes [Module Catalog] Add module images as additional Resources from sec-scanners-config.yaml #98

[medmes]

It looks good for me, the only thing is I have a concern about the create Service:

internal/service/create/create.go:65

It handles a lot of responsibilities, module configuration, git sources, security configuration, component archives, registry operations, module templates, CRD parsing, and file resolution.

But I think, we can work on it in a separate issue. What do you thinnk?

[c-pius]

It handles a lot of responsibilities, module configuration, git sources, security configuration, component archives, registry operations, module templates, CRD parsing, and file resolution.

But I think, we can work on it in a separate issue. What do you thinnk?

Thanks! I have some doubts that there is a significant improvement possible. Eventually, The Run of create.go is a orchestration function that just composes the overall flow of functionality and delegates execution to the specific services. But if you have an idea how we can improve this we can try :)

[medmes]

Yes,As we discussed maybe we can think about another naming if It's an orchestrator and not a in a sense of a service. I will rethink about potential naming to this encapsulating struct. Thanks Christoph!