Fix out-of-scope elements inheriting other elements' findings in resolve()

[NoodlesNZ]

TM.resolve() was assigning the in-progress findings list to out-of-scope elements instead of skipping them:

  if not getattr(e, "inScope", True):
      e.findings = findings
      continue

Since findings accumulates as the element loop runs, any element with inScope=False ended up with a copy of every finding generated for elements processed before it. Reports then showed findings against the exact elements that were declared out of scope, targeting completely different parts of the model.

The existing test_resolve didn't catch this because its out-of-scope actor happened to be created before any finding-producing elements, so the leaked list was still empty at that point. Element creation order determines iteration order in resolve(), so the bug only shows up when an out-of-scope element is defined after in-scope ones.

Changes:

• resolve() now sets findings to an empty list for out-of-scope elements. This also clears stale findings if a model is resolved again after flipping an element out of scope.
• Parametrised test_resolve to cover both creation orders (out-of-scope element defined first and last), so the leaking variant stays covered.