core: Use defines instead of magic numbers

The error-handling code should use the defines instead of magic numbers.
Remove documentation about Node API

Node API was never implemented.
AVDTP: Fix leaking remote sep capabilities

124 (32 direct, 92 indirect) bytes in 2 blocks are definitely lost in loss record 220 of 259
   at 0x4A0884D: malloc (vg_replace_malloc.c:263)
   by 0x4C7F2BE: g_malloc (in /usr/lib64/libglib-2.0.so.0.3200.3)
   by 0x4C936B1: g_slice_alloc (in /usr/lib64/libglib-2.0.so.0.3200.3)
   by 0x4C949F2: g_slist_append (in /usr/lib64/libglib-2.0.so.0.3200.3)
   by 0x1376D6: caps_to_list (avdtp.c:1325)
   by 0x13CA2F: session_cb (avdtp.c:2881)
   by 0x4C796E4: g_main_context_dispatch (in /usr/lib64/libglib-2.0.so.0.3200.3)
   by 0x4C79A17: ??? (in /usr/lib64/libglib-2.0.so.0.3200.3)
   by 0x4C79E11: g_main_loop_run (in /usr/lib64/libglib-2.0.so.0.3200.3)
   by 0x11FF72: main (main.c:545)
audio: Fix possible crash while exitting

This was probably introduced by a0f543f0eb8ee35f5cfac3b86f0a88e3f01809ff
as it changes the order now media is unloaded before control causing:

Invalid read of size 8
   at 0x13D743: media_player_free (media.c:987)
   by 0x12F942: player_destroy (avrcp.c:1340)
   by 0x4C94B0C: g_slist_foreach (in /usr/lib64/libglib-2.0.so.0.3200.3)
   by 0x4C94B2A: g_slist_free_full (in /usr/lib64/libglib-2.0.so.0.3200.3)
   by 0x1307E7: avrcp_unregister (avrcp.c:1358)
   by 0x1249CB: avrcp_server_remove (manager.c:1075)
   by 0x4C94B0C: g_slist_foreach (in /usr/lib64/libglib-2.0.so.0.3200.3)
   by 0x179124: adapter_remove (adapter.c:2219)
   by 0x174F81: manager_cleanup (manager.c:285)
   by 0x11FFA2: main (main.c:391)
 Address 0x63dc990 is 32 bytes inside a block of size 40 free'd
   at 0x4A079AE: free (vg_replace_malloc.c:427)
   by 0x4C7F3CE: g_free (in /usr/lib64/libglib-2.0.so.0.3200.3)
   by 0x122442: remove_interface (object.c:564)
   by 0x122F89: g_dbus_unregister_interface (object.c:1247)
   by 0x124CC8: media_server_remove (manager.c:1112)
   by 0x4C94B0C: g_slist_foreach (in /usr/lib64/libglib-2.0.so.0.3200.3)
   by 0x179124: adapter_remove (adapter.c:2219)
   by 0x174F81: manager_cleanup (manager.c:285)
   by 0x11FFA2: main (main.c:391)
AVCTP: Make use of sendmsg to avoid copying data

This use sendmsg to send headers and operands in separated buffers
avoiding memcpy.
core: Fix using mgmt status values instead of HCI
AVCTP: Fix not zeroing out buffer

This could cause use of unitialized memory
TODO: properties & object manager are back on track for BlueZ 5
lib: Correct length name in write assoc struct

Correct name from assoc_length to remaining_length.
doc: remove ListAdapters()

This method was already removed from bluetoothd.
TODO: Mark fast connectable issue as resolved
audio: Fix minor coding style issues
time: fix byte position

The position of the "Time Zone" and "Daylight Saving Time" fields on
the Local Time Information characteristic was inverted. This commit
fix their position.
attio: Rename att_cleanup to attio_cleanup

Cosmetic change renaming attio cleanup function. attio prefix is more
suitable since attio implements GIOChannel abstraction in the top of
the GAttrib.
btio: Rescue lost errorneous numbers

The BT_IO_ERROR_* flags are not used for anything else and we just
loosing errorneous numbers set in the sockets that might be more
useful for handling specific errors.

A use case would be disconnect errors that should not allow BlueZ to
enable auto connections since the connection would never be possible in
some cases.

This patch removes BT_IO_ERROR_* flags and use the errors set in the
sockets instead. Now, the errors passed in connect/disconnect callbacks
should contain proper error numbers passed to them.
attrib-api: Remove local service hierarchy

Local GATT services will now share the same interface as remote
services.
attrib-api: Update introduction text

We do not have service objects anymore.
attrib-api: Remove GATT service hierarchy
attrib-api: Update Characteristic interface
attrib-api: Update Watcher interface methods

There are now two different methods for the interface. Only one method
is called, based on the "raw" setting being enabled or not when
registering the watcher.