Improve granularity of diki rule options

[AleksandarSavchev]

What would you like to be added:
Rule options should be revisited and where possible improve granularity of silence targets. For example rule 2001 of security-hardened-k8s should allow configuring accepted containers in addition to pods:

    - ruleID: "2001"
      args:
        acceptedPods:
        - matchLabels:
            foo: bar
          namespaceMatchLabels:
            foo: bar
          acceptedContainers: #improvement
          - foo
          justification: "justification"

Why is this needed:
Allow users to silence findings more precisely

[georgibaltiev]

/assign

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all issues.
This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Mark this issue as rotten with /lifecycle rotten
• Close this issue with /close

/lifecycle stale

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all issues.
This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close

/lifecycle rotten