refactor(misconf): Remove unused options

[simar7]

Description

These options aren't often used due to reasons described in the disucussion and can be deprecated.

Related issues

• Close refactor(misconf): Remove unused options #7849

Related discussion

• BREAKING CHANGE(misconf): Removing support for less commonly used Rego features #7961

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 Does that mean we should now only support deny rules? https://github.com/aquasecurity/trivy/blob/main/pkg/iac/rego/scanner.go#L388-L395

[nikpivkin]

combined is also mentioned in the documentation.

[simar7]

@simar7 Does that mean we should now only support deny rules? https://github.com/aquasecurity/trivy/blob/main/pkg/iac/rego/scanner.go#L388-L395

Yes, there's even a comment about this https://github.com/aquasecurity/trivy/blame/797b36fbad90b8e7f04e16e2cf08d6bdc0255ac7/pkg/iac/rego/scanner.go#L387

Actually I just realized we didn't issue an announcement for this change. I will prepare that first.

Discussion here: #7961

[nikpivkin]

@simar7 As we discussed earlier, will support for warn and violation rules be removed?

[simar7]

@simar7 As we discussed earlier, will support for warn and violation rules be removed?

Yes, is there something that I've missed in this PR?