Add BaseCommand.ChangeCanExecute()

[TheCodeTraveler]

This PR is base on community feedback from @maxkoshevoi: #709 (comment)

Description of Change

Because Xamarin.Forms.Command uses ChangeCanExecute(), adding ChangeCanExecute() to both AsyncCommand and AsyncValueCommand enables an easier, more seamless, transition from Xamarin.Forms.Command to Xamarin.CommunityToolkit.ObjectModel.AsyncCommand.

API Changes

Adds BaseCommand.ChangeCanExecute()

• BaseCommand.ChangeCanExecute() leverages BaseCommand.RaiseCanExecuteChanged()

Behavioral Changes

None, BaseCommand.ChangeCanExecute() leverages BaseCommand.RaiseCanExecuteChanged():

public void ChangeCanExecute() => RaiseCanExecuteChanged();

PR Checklist

• Has tests (if omitted, state reason in description)
• Has samples (if omitted, state reason in description)
• Rebased on top of main at time of PR
• Changes adhere to coding standard
• Updated documentation

[TheCodeTraveler]

Assigning to @jfversluis for review since he was looped into the original discussion: #709 (comment)

[pictos]

@brminnick since this PR makes an API Obsolete I think that is an API change, so will be better to target the develop branch. Thoughts?

[TheCodeTraveler]

@pictos It doesn't make an API obsolete. It adds an API, improving the migration experience from Xamarin.Forms.Command to AsyncCommand.

Users of AsyncCommand should continue using RaiseCanExecuteChanged. It is the recommended API in the docs and the API used in the samples.

This PR adds ChangeCanExecute() to allow for an easier migration from Xamarin.Forms.Command.

I originally attributed ChangeCanExecute with the [Obsolete] tag so that intellisense would nudge the user to use RaiseCanExecuteChanged without breaking their implementation of Xamarin.Forms.Command. It makes for a easy and pleasant developer experience to have code that still runs but to also have intellisense provide the recommended usage.

As a compromise to not adding [Obsolete] to the code base, I changed it to [EditorBrowsable(EditorBrowsableState.Never)]. This provides a similar migration experience, but without additional benefit of recommending the recommended API that the [Obsolete] attribute provides.

[pictos]

@brminnick my mistake so, thanks for explaining that. Yeah, I would say that we are good to go then.

Changed [Obsolete] to [EditorBrowsable]