Support changing the device name

[whot]

The 0xbb command can set the device name, we should work that into the API. Few questions to be answered first though:

• can the name be set during register only or anytime? - Name can be set any time
• if during register only, how to work this into the API? Possibly by having Register() take the name argument. - can be done during normal connection
• what came first, the poached egg or the fried chicken? - experts are divided on the question - but does the chicken comes from Kentucky?
• set-name support on the Spark - see wacom: add support for a set_name on the Spark #83
• set-name support on the Slate - see wacom: add support for a set_name on the Spark #83 -> same behavior than the Spark
• set-name support on the Intuos Pro paper

[bentiss]

Regarding the API, I think we should let the client handle most of the subtleties.
We should have a SetName(name) DBus call, and document that the name will be changed the next time the device connects, and then the bluez stack might see the change only at the next advertising report.

So basically, put some big warning: you can change the name, but you'll have to keep your internal state yourself.

[bentiss]

One other solution, as the Android app has no issue setting the name during register. Register() takes the name as an argument, and once we are doing the second part of registering (where we check on the firmware and name, we set the name here). The bluez stack might notbe updated still, so we still need to tell the client to check on the internal state