`RefreshView` can have a memory leak with a custom `ICommand`

[jonathanpeppers]

Description

This problem can be illustrated with a test such as:

main...jonathanpeppers:RefreshViewLeak

If you create a custom ICommand on something like a singleton ViewModel, and use it on a RefreshView, the RefreshView will live forever.

I think this is lower priority, as the customer samples I've seen use Command or Command<T>:

maui/src/Controls/src/Core/Command.cs

Lines 113 to 117 in 49d22ac

	public event EventHandler CanExecuteChanged
	{
	add { _weakEventManager.AddEventHandler(value); }
	remove { _weakEventManager.RemoveEventHandler(value); }
	}

And WeakEventManager sidesteps this problem.

If we fix this, it might be worth auditing all properties of type ICommand.

Steps to Reproduce

1. Create a custom ICommand
2. Use it on RefreshView
3. RefreshView lives forever

Link to public reproduction project repository

main...jonathanpeppers:RefreshViewLeak

Version with bug

8.0.0-preview.5.8529

Last version that worked well

Unknown/Other

Affected platforms

iOS, Android, Windows, macOS, Other (Tizen, Linux, etc. not supported by Microsoft directly)

Affected platform versions

All

Did you find any workaround?

Use Command.

Relevant log output

No response

We've added this issue to our backlog, and we will work to address it as time and resources allow. If you have any additional information or questions about this issue, please leave a comment. For additional info about issue management, please read our Triage Process.