TaskExtensions: Rename AndForget() to CatchAndLog()

[henon]

Description

The name Task.AndForget() implies discarding the task. However, AndForget() does something very important, it observes the task in the background and catches any exceptions which are then forwarded to the global unhandled exception handler in MudGlobal. If we can not await a task we should never simply discard it like this: _ = SomeMethodAsync();. Instead we should do SomeMethodAsync().AndForget();. To make the significance of not discarding more evident I renamed the method AndForget to CatchAndLog ...

SomeMethodAsync().CatchAndLog(); ... discards the task in a safe manner.

Type of Changes

Refactor

[codecov]

Codecov Report

Attention: Patch coverage is 90.00000% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 90.45%. Comparing base (28bc599) to head (fecb963).
Report is 190 commits behind head on dev.

Files	Patch %	Lines
...MudBlazor/Components/DataGrid/MudDataGrid.razor.cs	0.00%	1 Missing ⚠️
...rc/MudBlazor/Components/Input/MudDebouncedInput.cs	50.00%	1 Missing ⚠️
src/MudBlazor/Components/Mask/MudMask.razor.cs	50.00%	1 Missing ⚠️
...ontentNavigation/MudPageContentNavigation.razor.cs	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #8950      +/-   ##
==========================================
+ Coverage   89.82%   90.45%   +0.62%     
==========================================
  Files         412      419       +7     
  Lines       11878    12196     +318     
  Branches     2364     2381      +17     
==========================================
+ Hits        10670    11032     +362     
+ Misses        681      629      -52     
- Partials      527      535       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[danielchalmers]

Name is not obvious about its intent to me at least. Something like FireAndForwardExceptions is longer but more self-explanatory and this method should be used sparsely anyway

[henon]

Catch is pretty self explanatory, no need to explain it. Log as well, it expresses that exceptions are not discarded (as oposed to Forget which hints at discarding) and I think Log it is better or at least as good as Forward. If we want maximum self-explanation we'd have to do DontAwaitButExecutInBackgroundAndCatchExceptionsAndForwardToGlobalExceptionHandler but I rather prefer a short and sexy name such as CatchAndLog which includes the most important details. It is self-evident from the code that we don't await, no need to express this in the name (that's also why I don't like AndForget which hints at the phrase fire-and-forget).

[henon]

ObserveExceptions() would also be a good one

[henon]

Or DiscardAndObserve()