Experimenting with push of detailed view
Propotyped subviews

- additional debug waypoints
Temporarily enable debug waypoints for reviewers
Utility waypoint un/boxing
Refactoring to allow push of (mission item) detail view on table view

- WaypointsViewController is no longer a TableView source/delegate
- now holds a container view, which embeds a UINavigationController
with a root controller of MissionItemTableViewController (a newly
introduced controller class)
- all tableView source/delegation has been moved from
WaypointsViewController to this new controller
- on edit row selection, MissionItemTableViewController pushes/performs
storyboard segues to instantiate the detailed view (for now,
essentially a static view with a UIPickerView for command type)
Minor terminology correction

Changed Waypoints -> Mission in select places
Fixed bug with segue misname

- set title on detail view
- refined table heights
Initialize selected picker view row to selected mission item type
Switch to "correct" mission item detail view based on command id/picker view
Switched over to page curl

- alternative hidden bar height fix
Refactoring to allow generic mavlink_mission_item editing

- removed tabbar controller and proposed per item-type views
- MissionItemEditViewController now has a UITableView, which populates
with label/textfield pairs based on meta-data associated with the
mission item type
Fleshed out list of mission types

- sanity checked
Slide mission item map and table up/down with keyboard display/hide

- ensures fields being edited remain in view when the keyboard is
introduced
Set textfield trait to numberPad

- avoids having to hit the "123" button to switch to numeric
Push UITextField edits into the respective field of the mavlink_mission_item
Hide nav bar in (contained) table view, but show in the detailed view

- better use of map/table editing real-estate
Enabled save/cancel of mission detail view edits
Prevent Done action while editing a mission item
Correct edge case of changing picker view while editing
Synchronized map and detail edits

 - synchronizing and reverting changes between the map and detail view
proved to be simpler by holding a token (in this case, an index) to the
mission item in the source data set and using in-place mutation (and
caching the original mission item for the "Cancel" case)