Make attributes more consistent in controllers

LoadBalancerController: Add attr_reader :routes and :active_routes because
all subclasses are expected to have them.  Add a comment explaining that
:routes, :active_routes, and :monitors are all arrays of strings.

F5LoadBalancerController, AsyncLoadBalancerController: Delete attr_reader
:routes, :active_routes, and :monitors because they now all come from the
superclass.

F5LoadBalancerController::Pool, AsyncLoadBalancerController::Pool: Delete
attr_reader :members, :name, and :monitors because they all come from the
superclass now or (in the case of :monitors) should not be in the Pool
class.
Delete monitor on app delete if it's not shared

daemon.rb: When deleting an application, if the application has a monitor
and the monitor is specific to that application, then delete that monitor.

To determine whether the monitor is specific to the application, use the
heuristic of checking whether the template for the name includes the
formats for application name and namespace.