Use ArgumentOutOfRangeException.ThrowIf* to replace custom error messages

[halgab]

This is a followup to #8403.

Description

Many error messages can be replaced with messages from the BCL using the new ArgumentOutOfRangeException throw helpers.
Here are the messages I removed, each in its own commit:

• ParameterMustBeGreaterThanZero
• ParameterCannotBeNegative
• ParameterCannotBeGreaterThan
• ParameterCannotBeLessThan
• ParameterValueMustBeGreaterThanZero
• ParameterValueCannotBeNegative
• ShouldBeZero

ParameterMustBeBetween would be a good candidate, but this would slightly change the information conveyed by the error message. I still think it's worth it though.
ParameterValueCannotBeInfinity and ParameterValueCannotBeNaN also come to mind.

Customer Impact

Slight performance improvement, and a bit fewer resources.

Regression

No

Testing

CI

Risk

Low. I manually searched and removed the error messages, and let CA1512 finish the work

Microsoft Reviewers: Open in CodeFlow

[rchauhan18]

Hey @halgab , I think we also need to update these changes to the files below:

https://github.com/dotnet/wpf/blob/main/src/Microsoft.DotNet.Wpf/src/UIAutomation/UIAutomationClientSideProviders/MS/Internal/UnsupportedAutomationProxies/windowspager.cs
Line: 53-56

https://github.com/dotnet/wpf/blob/main/src/Microsoft.DotNet.Wpf/src/UIAutomation/UIAutomationClientSideProviders/MS/Internal/UnsupportedAutomationProxies/WindowsDateTimePicker.cs
Line: 59-63

[halgab]

I kept those because of the asserts. But I'd be happy to make the change!

[halgab]

I kept those because of the asserts. But I'd be happy to make the change!

Actually that's not true. Those fell off my radar because they're not part of the solution. I'll make the change.

[rchauhan18]

Thanks @halgab for contributing!