Flow Classification Rule outcome calculator needs to be direction aware

[davidwatkins73]

Changes needed (at first glance)

Step	Changes Needed
1	Needs to discriminate between direction (possibly just a param)
2	This should probably be all under a tx (but may be slow)
3	Would need the direction from 1 propagating to it
4	Needs to know which field to target on the decorator table (outbound or inbound rule ref)
6	As 4

[davidwatkins73]

Rewrtiting the evaluator to prevent hundreds of database interactions (see step 5).
Initial outlook is good - now only takes 10 seconds (as opposed to several minutes).

I made a further attempt to speed it up by removing flows which could not be covered by any statement because there are not statements for the flows datatypes. This only reduced the flow population by a small amount, therefore the increased complexity is not worth the minor performance lift. The code I tried (and am now removing is repeated below (just in case!)

        HashSet<Long> allInscopeDTIds = ruleVantagePoints
                .stream()
                .map(FlowClassificationRuleVantagePoint::dataType)
                .distinct()
                .reduce(
                        new HashSet<Long>(),
                        (acc, dt) -> {
                            acc.addAll(findChildren(dtHierarchy, dt.id()));
                            return acc;
                        },
                        (a, b) -> {
                            a.addAll(b);
                            return a;
                        });

        Set<FlowDataType> inScopePopulation = SetUtilities.filter(population, p -> allInscopeDTIds.contains(p.dtId()));
        LOG.debug("Initial Population: {}, Trimmed Population: {}", population.size(), inScopePopulation.size());