Apply Accessibility traits to controls that have TapGestureRecognizers

[PureWeen]

Description of Change

If users attach a touch gesture recognizer that will activate with a single touch then we add accessibility traits that will inform readers that the element is clickable.

Move all the semantic processing logic to extension methods to allow users to reuse if they need to

Make the MauiAccessibilityDelegate public for reuse

Adds an AccessibilityDelegateCompatWrapper that wraps an already assigned AccessibilityDelegateCompat. This allows you to easily retain the behavior of the current delegate and then add on to it

Alternative PR to
#1861

Additions made

// Contains logic for adding accessibility info if you're using a touch gesture
public class ControlsAccessibilityDelegate : AccessibilityDelegateCompatWrapper

// Allows users to call our code as an extension if they want to reuse any of our logic
// from their own custom code
namespace Microsoft.Maui.Controls.Platform
{
	public static class SemanticExtensions
	{
		public static void UpdateSemanticNodeInfo(this View virtualView, AccessibilityNodeInfoCompat? info)

// This allows you to take the existing delegate and wrap it if you want to retain
// the behavior of the Accessibility Delegate that's already assigned to the control
// We use this inside controls if we want to add additional accessibility delegate behavior
namespace Microsoft.Maui
{
	public class AccessibilityDelegateCompatWrapper : AccessibilityDelegateCompat
	{
		public AccessibilityDelegateCompatWrapper(AccessibilityDelegateCompat? originalDelegate)
		{
			_originalDelegate = originalDelegate ?? BlankDelegate;
		}

// Made our delegate public if users want to reuse it
public class MauiAccessibilityDelegateCompat : AccessibilityDelegateCompatWrapper

PR Checklist

• Targets the correct branch
• Tests are passing (or failures are unrelated)
• Targets a single property for a single control (or intertwined few properties)
• Adds the property to the appropriate interface
• Avoids any changes not essential to the handler property
• Adds the mapping to the PropertyMapper in the handler
• Adds the mapping method to the Android, iOS, and Standard aspects of the handler
• Implements the actual property updates (usually in extension methods in the Platform section of Core)
• Tags ported renderer methods with [PortHandler]
• Adds an example of the property to the sample project (MainPage)
• Adds the property to the stub class
• Implements basic property tests in DeviceTests

Does this PR touch anything that might affect accessibility?

• Does this PR introduce a new control? (If yes, add an example using SemanticProperties to the SemanticsPage)
• APIs that modify focusability?
• APIs that modify any text property on a control?
• Does this PR modify view nesting or view arrangement in anyway?
• Is there the smallest possibility that your PR will change accessibility?
• I'm not sure, please help me

If any of the above checkboxes apply to your PR, then the PR will need to provide testing to demonstrate that accessibility still works.

[rachelkang]

nice!

[rachelkang]

LGTM!