30985:Fix FlyoutPage Navigating args to not reach down into the NavigationPage

[SuthiYuvaraj]

Note

Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!

Description of Change

This PR updates the PageDetail property in FlyoutPage.cs.
The change simplifies the navigation logic by:

• Removing the NavigationPage unwrapping.
• Replacing the explicit null-check with the null-conditional operator.
  With this update, SendNavigatingFrom is invoked directly on the current value.

Related PR
PR Link #28384

Issues Fixed

Fixes #30985

Tested the existing UI and DeviceTest in the following platforms

• Android
• Windows
• iOS
• Mac

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Copilot]

Pull Request Overview

This PR simplifies the navigation event handling logic in FlyoutPage by removing NavigationPage unwrapping and streamlining the code. The change ensures that navigation events (SendNavigatingFrom, SendNavigatedFrom, and SendNavigatedTo) are called directly on the actual Page objects rather than attempting to unwrap NavigationPages to get their current pages.

Key changes:

• Removes complex NavigationPage unwrapping logic that was extracting CurrentPage from NavigationPages
• Simplifies null checking using the null-conditional operator
• Updates navigation event arguments to pass the actual Page objects directly

[PureWeen]

@SuthiYuvaraj can you add some unit tests for this change?

There should be a pretty large set of unit tests (not UI tests) already testing this feature

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jsuarezruiz]

/rebase

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[PureWeen]

@SuthiYuvaraj it looks like the test failure might be real?
PullToRefreshWorksWhenEnabled

Or we need to rebase this?

[SuthiYuvaraj]

@PureWeen, This failure is due to a flaky test case (PullToRefreshWorksWhenEnabled) and is not related to my changes. We can try rerunning the CI.

[PureWeen]

/rebase

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).