feat(misconf): register builtin Rego funcs from trivy-checks

[nikpivkin]

Description

Related issues

• Close fix(misconf): split docker commands by semicolon #6516

Related PRs

• fix(rego): improve commands parsing trivy-checks#113

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[nikpivkin]

@simar7 I have my doubts about the choice of repository to host the additional Rego funcs. On the one hand they are only related to checks, so it makes sense to put them there, but on the other hand we already register some Rego functions in trivy. Now I'm leaning towards the second option, because with the first option we will have to move these functions sooner or later when we migrate checks from Go to Rego.

[simar7]

@simar7 I have my doubts about the choice of repository to host the additional Rego funcs. On the one hand they are only related to checks, so it makes sense to put them there, but on the other hand we already register some Rego functions in trivy. Now I'm leaning towards the second option, because with the first option we will have to move these functions sooner or later when we migrate checks from Go to Rego.

Personally I see the rego functions as a library for the rego checks so to me keeping them with the checks repo makes more sense TBH. We could reconsider this in the future when the transition of Go checks to Rego actually takes place.

On that note, we could make the custom functions into a library and have them all be imported into Trivy from the trivy-checks repo. What do you think about that?

[nikpivkin]

@simar7 I agree. I think we can move custom functions from trivy to trivy-checks.