[Metrics] Cast the parameter for avoiding ambiguity in a new atom

When adding a new atom BluetoothContentProfileErrorReported, it
introduces an ambiguity when using stats_write native method.
This CL fixes the issue.

Bug: 294797589
Test: m -j
Ignore-AOSP-First: Atom definition must be done first in internal main
Change-Id: Iaed9bf788e5e9a04cd866e302e73ea21bdd8f769