Let a module opt out of the redundant stated IsA policy

[dionmcm]

Redundantly-stated IsA is an editorial policy, and not every edition has adopted it.

AMT and AU clinical content state redundant IsA relationships because they do not follow the proximal primitive modelling pattern - this has been discussed many times, there are pros and cons and it is a design choice.

Currently the rules don't enable this design choice, reporting it as failures.

Change

The rule fires for every module except those listed under redundant-isa-exempt-modules in the test resources.

Behaviour is unchanged for any module not listed in this resource. This allows extensions to optionally opt out of this rule for just their module content while still allowing the rule to run where it should.

Depends on isInNamedSet

The rule needs a way to read a set of module ids from reference data. Rules can currently reach that store only through isSemanticTagCompatibleWithinHierarchy, which extracts a semantic tag from a term first, so a module id cannot go through it.

isInNamedSet on DescriptionService is the companion change. It is defaulted so implementations outside the project keep compiling, and the default answers false so this rule keeps firing everywhere on any implementation that has not adopted it.

This means the rule cannot be merged before a release carrying isInNamedSet. A rule calling a method the deployed engine does not have fails at KieBase build, which takes down the whole rule set rather than this one rule.

Verification

722,404-concept edition, rule sets common-authoring,au-authoring, same reference data both times except for the one added line:

	findings
key absent	352,500	byte-identical to unmodified rules
redundant-isa-exempt-modules=32506021000036107	346,263	6,237 dropped, 0 added

Every one of the 6,237 is on the module named in the key. The 287 findings on inherited international core-module concepts are all still reported.

The dropped set is identical to the set the core-module version dropped, so the change in mechanism costs nothing in outcome for this edition.

Test cases

The rule directory's test-cases.json had empty assertConceptsPass and assertConceptsFail arrays so no coverage. Added a fixture - a grandparent, a parent stated under it, and a concept on an extension module stating both.

• With no redundant-isa-exempt-modules key, the rule fires. That is the safety property, tested.
• Add the module to the key in the test resources and the rule goes quiet, and the fixture reports "a concept from the assertConceptsFail set actually passed". Proves opt-out works.

RulesTestManual runs 109 rule directories, all pass with this change.

This needs TestDescriptionService.isInNamedSet, which is part of the engine PR - without it the rig only ever sees the interface default and no named-set rule can be tested configured.