No mbpi add custom

This change does the following:

 - it renames the android-provision plugin to ubuntu-provision
 - it renames the helper android-apndb.* files to ubuntu-apndb.*
 - it removes support for the mbpi database
 - it adds support for customization via /custom/etc/apns-conf.xml
   ( https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1315509 )

The custom file is read first, and if any mvno matches are found, provisioning ends ( ie. /system/etc/apns-conf.xml is not queried ).  If no mvno matches are found, then the /system file is next queried.  If any mvno matches are found, the list is trimmed to just those matches.  Finally the two lists are merged.  If an apn is found in /custom which matches the type and 'apn' attribute of a /system apn, then the custom one is used.

This has been tested on mako, running image #u132.
To be honest, the purpose of the custom DB is still a bit fuzzy for me. I do not think that the use case that was mentioned in the mail thread is really covered, but well, if the agreement was to to provide a custom DB then the logic can be fine either as it is or changing it no not return here.