bluetooth: backend-native: Handle RegisterProfile failure

Try to register profile support again after RegisterProfile fails, when
BlueZ indicates no one else is implementing the profiles we are
interested in.

Ideally this would rely on a list of UUIDs supported by the profile
manager instead of the adapter, but BlueZ has no such API.

Part-of: <pulseaudio/pulseaudio!593>
2 jobs for for-upstream/handle-bluetooth-profile-registration-failure in 2 minutes and 41 seconds (queued for 1 second)