Add a view for the Methods section.
Add a view for the Fields section.
Use _.size for object length and move event binding into the view.
Add Resource and Method collections, and a SelectedResource model.

The collections are tiered, and will hold all the api data at all times.

The new model will hold the data for the currently selected resource (there will be a new model for the selected method too, soooon). This controls the rendering of selected resources in the list, and will be used to create the request api at a later time.
Have the Methods list listen to the SelectedResource and re-render as needed.
Fix keyboard next/prev for the resource list.
Fix global that renders the Method Fields.
Remove unused `selected` attributes.
Fix XML request generation
Use better names within the views for the data sources
Cleanup Method and Field classes.

Don't need view vars until render() happens
Let the Methods view set the method field on the selectedResources model

This event will be something the Fields view can listen for.
Remove the currentResource and currentMethod globals.
Render the selected method in the view class.
Rendering the Fields list is triggered by an event, not a direct call.
Remove a global call from Views/Resources.

Also a console.log is gone
Make sure cycleAnchor keeps working
New model/collection strategy without an explicit Selected model.

Although the initial loading and change:is_selected has some small magic, all the rest of the app is much easier to reason about with two parallel lists of things (like db tables!) that refer to each other.
Init all views inside of the AppView object.

This will make a nice target for things like the keyboard click events and cycleAnchor()
Move keybindings into the AppView.