Generalize rescoring rule model

[TuanAnh17N]

What this PR does / why we need it:

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Release note:

[ccwienk]

could you elaborate on the highlevel organisation of rulesets you suggest?

before this change, there was a global (cve-)rulesets, which was a list of (cve-)rescoring-rules.

or. yaml-ishly speaking:

rulesets: # each entry implicitly being a set of cve-rescoring-rulesets
 - name: my-rescoring-rules
   rules: # list of rules

In that example, the topmost attribute (rulesets) might be described /w a typehint list[CVE_RescoringRuleset, ...] whereas each CVE_RescoringRuleset would have a list (stored in rules) of CVE_RescoringRule

--

After the ongoing generalisation, I think we should have something like:

rulesets:
- name: my-cve-ruleset
  type: cve-rescoring
  rules: # cve-rescoring-rules
- name: my-sast-ruleset
  type: sast-rescoring
  rules: # sast-rescoring-rules

Thus, it will make sense to have a (generic, ideally w/ type-params) base-class for rulesets, and rulesettype-specific rules, like so (pseudo-pseudo-code - I might have gotten type-parameters wrong syntactically):

class Rule:
  name: str # probably, each rule should have a name

class RuleSet[T: Rule]:
  rules: list[T]

class CveRescoringRule(Rule):
   pass #...

class SastRescoringRule(Rule):
  pass # ...

class CveRescoringRuleset(Ruleset[CveRescoringRule]):
  pass