Force AttributionSource after handler dispatch.

The Bluetooth stack often receives BluetoothDevice instances from
remote Binder calls, and previous work forced the AttributionSource
to match that remote caller.

However, in some instances these objects are passed to an internal
handler or state machine, and we need to switch back to our internal
AttributionSource, since any method calls will be performed as the
Bluetooth stack.

Longer term we should find a better way of transporting these
values in AIDL directly, but this is the safest mechanical change
to make at this late stage of the release.

Bug: 193194829, 188391719
Test: atest BluetoothInstrumentationTests
Change-Id: I19649edb72aabeb92d4987739a1c4cd7fa07bb21