Adding logging Branch
Adding more verification tweaking input fields

added more verification to option moving and collision as well as menu
selection, tweaked more input and action fields to understand flow
easier, also added more detailed logging for display of menu options
Log Menu Selection now stores objID

1. Added identifier to all images when creating menuItem to store the
objID
2. LogMenuSelection now stores the objID instead of the image pointer.
3. Logs in format <Menu Item 1>  objID, objID, objID, interaction <Menu
Item 1/>
4. Working out error with printing sometimes prints next menu item
values
Fixed Menu Selection Logging

1. Menu Selection Logging now correctly logs each object in the menu
selection with the associated interaction type.
TODOS: Working on adding a better way to distinguish the relationship
between the menu items currently if a menu item has the same objects
and interaction type there is no way to distinguish them. Idea is to
extract the action from the relationship and log that.

Also enable the displayMenu computer action, currently only selection
is enabled which is the user action of selecting a menu. Displaymenu
will be the computer action upon correct user action of moving an
object to the correct other object location.
Code Clean up, log display menu added, more verifi

1. Code Clean up removing commented out and outdated segments of code
as well as removing log statements from testing purposes
2. Added logging of display menu, records when the menu is first
displayed, and when a user selects a menu item logs seperately
3. Added more verification functions for move object to object and move
object to hotspot location
4. Added logging function for swapping of images in menu item data
source
Changing terminology, expanding menu display and selection details, simplifying log output data

1. Changed ContextualMenuDataSource and MenuItemDataSource to now also
record the relationship associated with that menu item. To do so I also
had to change the function simulatePossibleInteractionForMenuItem in
pmviewcontroller and possibleinteractions. Possbieinteractions now
creates the array that holds all relationships for the possible
interactions for the correct possible solutions.
2. Added variables to hold collision objects and most recent
relationships parsed for easier access for logging which objects are
being collided into.
3. Changed the structure of the display menu and selection of menu item
functions to now record relationships to better distinguish which menu
items are which for menu items that have the same interaction and
images.
Todo:
1. More code cleanup (mostly removing slog debugging statements)
2. Further Simplification of logging structure format and making sure
input, selection and action fields are intuitive and consistent
3. Testing emergency swipe logging
4. Testing Word and object selection logging in introduction
5. Testing Multiple pages logging
6. Testing audio logging for language conditions
7. Complete test of all chapters
Fixing bugs with relationships added to menu items, code clean up, simplifying logging structure and naming conventions, flushing out logging word presses and emergency next swipe

1. Fixed bug with adding relationships to menu items that was causing
the system to crash, also added a reset for populating relationships
2. Flushed out logging word presses (needs to be tested on full merge
of Introduction Branch)
3. Flushed out Emergency Swipe logging (needs to be tested on merge)
4. Changed Verification to be more detailed
5. Added collision Objects to moving objects
6. Further simplification of logging structure and naming conventions
7. Code clean up
Merge remote-tracking branch 'origin/LoggingBranch' into IntroductionBranch
Merged changes from LoggingBranch