Follow-up Migrate data processing in scan result policies to its own utils

The following discussion from !123052 (merged) should be addressed:

• @f_caplette started a discussion: (+1 comment)

  Suggestion - follow-up This is clearly out of scope here, but the whole computation here should probably be moved to its own util function. That way we could quite easily test it as a standalone function and remove quite a lot of logic from the component, WDYT?