Look at making accessibility properties a NOOP for some invalid cases on iOS

### Description

On iOS it's not a recommended or functional approach to apply accessibility properties to layouts unless you are making a semantic control. Scenarios like applying a Semantic Description that work for `Android` and `WinUI` don't yield the same result for iOS.

It's always a tricky trying to be "too smart" with APIs but for a case like the CollectionView there isn't really a valid scenario to apply an entire description to the `UICollectionView`.

The motivation to make this a noop is primarily for users that don't test accessibility after they apply properties. Not applying this property leaves the app in a less broken state then applying the property. Both outcomes are seemingly wrong from the users perspective but applying it is completely wrong for the user.

If the developer wants to use their "better judgement" They can just apply the accessibilityLabel themselves to the underlying control or use a mapper to replace our behavior

Start by reproducing the Semantic Description behavior on a CollectionView backed by UICollectionView on iOS, then compare it with the Android and WinUI behavior described in the issue. Done means invalid accessibility properties become no-ops on iOS while developers can still set the underlying control's accessibilityLabel or replace the behavior with a mapper.

Written by the indexing model from the issue text.