split detection needs tighter integration with other rule processing results

[jazdrv]

noticed something today where I needed to do this, so I put in some code to consider all POS suggestions (with existing POS's) as the criteria for a consistency check.

but really, it needs to be even smarter.

for example, it could be that just some of the POS suggestions are useful. and others if used, would cause inconsistencies (split recommendations).

so, far this is the recent sha update with part of this solution that I posted today. (but still more needs to be done)

• 994099d - Zak Jones, 21 minutes ago : resolved an issue where split rule processing logic wasn't considering projected positive promotions based on other rules

[jazdrv]

I mis-labeled the issue I was working against in my git comment. I meant #22. Not #23.

• da3b1a4 - Zak Jones, 77 seconds ago : Issue #23 ... needs to be tested and a great deal of code cleanup, but I think this is getting much closer

Might even resolve this particular issue...