Always expose members and name attributes of Pools

Add attr_reader :name to F5LoadBalancerController::Pool, and add
attr_reader :members, :name to AsyncLoadBalancerController::Pool.
Don't use splat on singletons

Turns out that the * "splat" operator behaves differently between Ruby
1.8 and Ruby 1.9.  In particular, *[foo] evaluates to foo in Ruby 1.8,
but it evaluates to [foo] in Ruby 1.9.  So use an explicit array index
where we have a singleton array.
oo-admin-load-balancer: send update

Don't forget to invoke the update method on the controller!
Make default {add,delete}_pool_member do something

Make the default LoadBalancerModel#add_pool_member and
delete_pool_members, respectively, so that add_pool_member and
delete_pool_member are useful even if a subclass defines only
add_pool_members and delete_pool_members.
Fix usage of create_route and delete_route
LoadBalancerConfigurationDaemon: Rename things

Use the more the more generic term 'route' rather than the F5-specific
terminology of 'profile'.

Rename pool_name_for_gear to generate_pool_name and drop the unneeded
parameters.  Rename profile_name_for_gear to generate_route_name and
drop the unneeded parameters for this method as well.
Change event names

Use :add_gear instead of :add and :delete_gear instead of :delete.

These event names are changing in the broker plug-in because we are
adding :create_application and :delete_application events as well.
Handle :create_application and :delete_application

Handle the new :create_application and :delete_application by creating
and deleting pools and routing rules as appropriate and stop performing
these tasks in add_gear and delete_gear.
Fix reading of DEBUG setting

The old logic of enabling debugging output iff the value of DEBUG is
true is wrong because the string 'false' is considered to be true.

Fix the read_config methods in the LBaaS controller and daemon code to
enable debugging output iff the value of DEBUG matches the string 'true'