Fix more memory-unsafe logging

In various locations around the stack, log statements use structures that
may, in exceptional cases, have been freed by preceding calls.  This can
lead to use after free and potentially to security vulnerabilities.

Use local variables instead, or store the length before the call if no
local variable is already convenient.

Bug: 375404242
Bug: 375398779
Bug: 375397720
Bug: 375397164
Bug: 375397370
Bug: 375396810
Bug: 375159652
Bug: 375160214
Bug: 375159480
Test: m libbluetooth
Test: researcher POC
Flag: EXEMPT trivial logic fix
Ignore-AOSP-First: security
Tag: #security
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:43cfd234de9ba9557118b0014513269cc1aeefda)
Merged-In: I6289907e86786eb2e10a163f7fb5d2557eab00bc
Change-Id: I6289907e86786eb2e10a163f7fb5d2557eab00bc