Fix getCanForwardToProfileIdMapInternal implementation to resolve cross profile access.

* Ensure that CrossProfileIntentForwarderActivity resolution is accurate.
  This relies on the @hide property `targetUserId` by accessing it via
  reflection as there is no API that can surface this information for
  `module_current` targets.
* Add test cases for devices that may be configured to have more than
  one managed profile, and may not be compatible with AOSP source code
  assumption to ensure CrossProfile detection fails closed.

Bug: b/394231676
Test: atest MediaProviderTests:UserManagerStateTest
Flag: EXEMPT bugfix
Change-Id: Id2a452e29218f9625d32a081ec8f0cf8508d2a0b