[Android] Implement ADPF hint sessions for API 35+ with AWorkDuration - #192582

• Gate ADPF hint session creation to Android 15+ (API 35+).
• Dynamically resolve AWorkDuration APIs and APerformanceHint_reportActualWorkDuration2 from libandroid.so.
• Report aggregate elapsed duration of CPU build and raster phases (build_ns + raster_ns), work period start timestamp, and total frame duration.
• Exclude MergedPlatformUIThread::kMergeAfterLaunch to avoid tracking stale UI thread after dynamic task queue migration.
• Manage reusable AWorkDuration instance synchronized under std::mutex with APerformanceHintSession.
• Fix target duration state caching to only update upon successful native PowerHAL return.
• Apply provisional 75% target frame-work ratio to leave scheduling slack while GPU duration is unmeasured.
• De-duplicate updateTargetWorkDuration calls to prevent redundant Binder IPC.
• Check NDK return codes, log warnings, and close session cleanly on EPIPE disconnects.
• Switch session creation log to FML_DLOG to avoid logcat pollution.
• Use explicit types instead of auto per Google C++ style and Flutter reviewer preference.

Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.

List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.

If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I signed the CLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant in-code documentation (doc comments with ///).
• If this PR introduces a new feature or capability, I created and linked a website documentation issue or PR in flutter/website (or verified none is needed).
• I added new tests to check the change I am making, or this PR is test-exempt.
• I followed the breaking change policy and added Data Driven Fixes where supported.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.