Fix InvalidCastException in Can/ConvertTo from MouseActionConverter

[h3xds1nz]

Mirrors #10289

Description

Sending this in now when we merged and discussed #9891 as I've discovered this bug during development of #9676 but wanted to wait until I can fix the TODOs in the unit tests as well.

Fixes InvalidCastException thrown from CanConvertTo when unboxing cast is performed on value that was not null but was of a different type than MouseAction or the underlying storage (byte), e.g. an object or a different value type (int).
Can* methods should not (and converters do not intentionally) throw in them but this is simple a programmer's error, it is not documented behavior either, hence the fix for this.

https://learn.microsoft.com/en-us/dotnet/api/system.windows.input.mouseactionconverter.canconvertto?view=windowsdesktop-9.0

Fixes the same issue in ConvertTo by throwing the proper (NotSupported) exception.

https://learn.microsoft.com/en-us/dotnet/api/system.windows.input.mouseactionconverter.convertto?view=windowsdesktop-9.0

Customer Impact

Less unexpected exceptions thrown.

Regression

No.

Testing

Local build, unit test.

Risk

There might be a concern that a code was passing byte instead of MouseAction which is the underlying storage type, so it survives the unboxing hard cast that was being performed but not the type is check. We may therefore for back-compat include check for both MouseAction and byte but other converters (besides Key since it shares the bug) just check for their type, so in my honest opinion it would be best to unify the behaviour and mention in release notes.

Not to mention, unlike Key where the backing storage is int, here its byte, even lesser chance for such occurence.

Microsoft Reviewers: Open in CodeFlow