Expose AutomationOption Setter for ChildSite

[vineethkuttan]

Description

#15611 This PR removed fragment based automation for content island that is connected using childsite.
This PR is exposes the automation option setter in builder.

Type of Change

Erase all that don't apply.

• Bug fix (non-breaking change which fixes an issue)

Why

This will make sure that other content island which will connected in childsite can customize their automation option

What

• Exposed the getter which set will set the childsite automation

Screenshots

xamlws.mp4

Testing

Tested in the SampleFabricApp

Changelog

Should this change be included in the release notes: yes

Expose AutomationOption Setter for ChildSite

Microsoft Reviewers: Open in CodeFlow

[acoates-ms]

We shouldn't be adding Xaml specific code like this.
The xaml case indicates that different controls may require FragmentBased or FrameworkBased automation options. I imagine a custom WPF control, if WPF adds support for ContentIslands would also want framework based. One option would be to add a property to the build to specify which you want. Alternatively, we could expose a getter for the ChildContentLink, so that the custom control can customize it as desired.

[vineethkuttan]

We shouldn't be adding Xaml specific code like this. The xaml case indicates that different controls may require FragmentBased or FrameworkBased automation options. I imagine a custom WPF control, if WPF adds support for ContentIslands would also want framework based. One option would be to add a property to the build to specify which you want. Alternatively, we could expose a getter for the ChildContentLink, so that the custom control can customize it as desired.

@acoates-ms exposed the setter for ChildSite Automation

[sundaramramaswamy]

Signed off with comments. Please handle them.