fix: corebluetooth peripheral name

[szymonlesisz]

as well described here peripheral local_name and advertisement_name are two different things and it is justified to keep them separated as situation that local_name is not equal advertisement_name could happen in all platforms and can be implemented later as followup.

currently it is quite unfortunate that the API changes the peripheral local_name (GAP) by joining those two values

changes:

1. added Peripheral.advertisement_name - default None
2. implement advertisement_name in corebluetooth

fix: #434

[tternes]

Thank you for working on this! I should be able to do some testing this week and share feedback.

[tternes]

I finally had a chance to test this in our setup. It works exactly as expected. Really nice solution.

Thanks @szymonlesisz!

[qdot]

Ok, this does seem like the correct thing to do, and probably should've been done from the start but we're still dealing with issues we inherited from forking 7+ years ago heh.

Main issue is going to be adapting it to the rest of the platforms so we're consistent, but I'll handle that.

[tternes]

Ok, this does seem like the correct thing to do, and probably should've been done from the start but we're still dealing with issues we inherited from forking 7+ years ago heh.

Main issue is going to be adapting it to the rest of the platforms so we're consistent, but I'll handle that.

I'm happy to help with testing when you have a PR ready.

[qdot]

@tternes It's actually sitting on dev now because I wasn't watching what I was doing heh. Feel free to give it a shot.