Details from CFA Jira Feature Request (INF-12243)

Add step to order guide rules logic to ensure items are removed from order guides if a restaurant is moving zones and the new zone does not have include logic for the item.

Per Will:

1. If we implement a change that removes an item, based on it being assigned to Zone A, but not Zone B, we should implement this for all available zone types (Location - xyz)
2. If an item is Excluded by a rule for Zone A, but not for Zone B, the item will be introduced at the restaurant (assuming that there is a rule in place to make it active)
3. If an item is Discontinued by a rule for Zone A, but not for Zone B, the item will be introduced at the restaurant (assuming that there is a rule in place to make it active)

Order Guide Notes

https://docs.google.com/document/d/1utfJ-0646KdJuT1JaM-14lQ_poEREA7QwOW3dtVI0vA/edit

Requirements Document Link

https://docs.google.com/document/d/11d-ESxCdQ4JP8vmLh2-kCncIAuYKXncokeh0ZgqQXeg/edit?usp=sharing

3. Scenarios for Order Guide Rules
https://docs.google.com/spreadsheets/d/1k5O7JOnEnRCH3K2OElfKcShJv59OKnVqXxDZChnIE1w/edit#gid=1952873911

Testing Guide:

The attached *TestRunner.sql files contain guides to set up and run the scenarios listed in the attached Order Guide spreadsheet.
The attached stored procedures must be on the database for the TestRunner files to work.
The *TestRunner.sql files contain instructions in the comments, but the overall process is:
0) run the cleanup stored proc
1) run the setup stored proc
2) run the scenarios to see the "before" applied state
3) open MxConnect to manually apply the rules that were just created (...#/Administration/AssignVendorItems/AssignVendorItems)
4) run the scenarios again to see the "after" applied state
5) run the cleanup stored proc