chore: new binding updates

[vatsashah45]

GitHub Issue (If applicable): closes #

PR Type

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior?

Updated the documentation with new binding updates.

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)

Other information

Internal Issue (If applicable):

[eriklimakc]

I'm not quite sure about this example here, does it still make sense? What would be the changes for this example regarding the API changes?

uno.extensions/doc/Learn/Markup/Binding101.md

Lines 174 to 185 in e0c7000

	new MyCustomControl()
	.DataContext(x => x
	.Source(this)
	.Binding(() => this.DataContext)
	.Convert(dataContext => {
	if (dataContext is MyViewModel myViewModel)
	{
	return new MyCustomControlViewModel(myViewModel.SomeContext);
	}
	return null;
	})
	.OneTime()

cc @dansiegel @nickrandolph

[nickrandolph]

@vatsashah45 I've approved these changes but I think we need to add some docs that point out the now deprecated Bind syntax and confirm that "Binding" is the equivalent of "Path" in XAML

[welcome]

Congrats on your first pull-request! We ❤ the people who are involved in this project, and we’d love to pay it forward by sending you some swag. If you have any feedback (or ideas how to improve Uno as a open-source project) please open a feedback issue.

Merci beaucoup 👋