[iOS] Fix CarouselViewRemoveAt so that it's passing on both CV1 and CV2 sets of handlers

[PureWeen]

Description

This test was modified to only run on CV2 because it's not passing on CV1
https://github.com/dotnet/maui/pull/25719/files

We need to fix it so the test is passing on both sets of handlers

[similar-issues-ai]

We've found some similar issues:

• [iOS] Fix CarouselViewLoopNoFreeze so that it's passing on both CV1 and CV2 sets of handlers #25775 , similarity score: 93%
• [iOS] Fix HeaderFooterGridHorizontal so that it's passing on both CV1 and CV2 sets of handlers #25774 , similarity score: 84%
• [iOS] Fix HeaderFooterGrid to pass on CV1 and CV2 #25773 , similarity score: 83%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[NirmalKumarYuvaraj]

Issue details

When using CV1 handlers, removing the first item from the CarouselView during navigation doesn't work as expected. The removed item remains visible in the view . This functionality works correctly with CV2 handlers.

Steps to Reproduce

1. Go to this file CarouselViewRemoveAt and Replace CarouselView2 with CarouselView1.
2. Run this test case.
3. Notice the first slide with text as 1 is still in the view.

Output

Expected	Actual
Handler2.mov	Handler1.mov