fix: avoid NumberFormatException on String > Integer.MAX_INT

[mikehardy]

Purpose / Description

In the settings -> backups section you can paste whatever you want (or type whatever you want) number-wise into the prefs

If you put something too large in there (like, 9999999999) then you'll crash

This uses an internal function already special built for this, to not crash

Fixes

https://ankidroid.org/acra/app/1/bug/249351/report/5d5ad546-4725-4cf3-b93f-b601b26f4cde

java.lang.NumberFormatException: For input string: "9638527410"
	at java.lang.Integer.parseInt(Integer.java:797)
	at java.lang.Integer.parseInt(Integer.java:915)
	at com.ichi2.preferences.NumberRangePreferenceCompat$NumberRangeDialogFragmentCompat.onDialogClosed(SourceFile:35)
	at androidx.preference.PreferenceDialogFragmentCompat.onDismiss(SourceFile:12)
	at androidx.fragment.app.DialogFragment$3.onDismiss(SourceFile:15)
	at android.app.Dialog$ListenersHandler.handleMessage(Dialog.java:1480)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:224)
	at android.os.Looper.loop(Looper.java:318)
	at android.app.ActivityThread.main(ActivityThread.java:8777)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:561)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1013)

Approach

Realize we already had a safe String-to-int function, expose it for use, use it

How Has This Been Tested?

Reproduced the crash locally, doesn't crash after
Reproduced all other number dialog and increment dialog behavior after, seems to work

Learning (optional, can help others)

Users are monkeys and they'll input anything (but it's okay, I'm a monkey too)

Checklist

Please, go through these checks before submitting the PR.

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner