Remove FROM_HERE from do_in_jni_thread invocations

In production FROM_HERE only convey the filename
and the pc and only log the pc in case of internal
libchrome failures.

It's mainly useful in debugging by enabling
ENABLE_LOCATION_SOURCE and logging the
base::Location object ourselves.

The same information can be retrieved using c++'s
[source_location](https://en.cppreference.com/w/cpp/utility/source_location)
without needing to modify every caller.

The benefit outweight the cost of needing to provide
that (correctly) in every call site.

Bug: 345074109
Test: mmm packages/modules/Bluetooth
Flag: EXEMPT mechanical refactor
Change-Id: I5ba252baa6c885f3c34bffec058517bf39539bbe