Copy KeyCharacterMap object when we fill InputDeviceInfo(2/n)

Currently, in InputDeviceInfo, we store the KeyCharacterMap object,
which is actually the original KeyCharacterMap from the EventHub. This
could potentially lead to issues where two threads operate on the same
KeyCharacterMap object simultaneously, resulting in thread safety
problems.

To avoid potential risks in the future, we make a copy of the original
KeyCharacterMap when generating InputDeviceInfo.

This change should not introduce any behavioral changes.

Bug: 373011069
Flag: EXEMPT refactor
Test: presubmit

Signed-off-by: Linnan Li <lilinnan@xiaomi.corp-partner.google.com>
(cherry picked from https://partner-android-review.googlesource.com/q/commit:39ba793d57aebda3dd7c3caa1b2e18464c3a6d28)
Merged-In: Icd18de9d2df1a95c83c8c06bfaef05fb73e1691b
Change-Id: Icd18de9d2df1a95c83c8c06bfaef05fb73e1691b