Warn user when adding media files exceeding the AnkiWeb size limit

[ujjol1234]

Purpose / Description

This PR implements a warning dialog when a user attempts to add a media file that exceeds the AnkiWeb synchronization limit (100MB).

Fixes

• Fixes Warn users on attaching media files which breach the AnkiWeb limits (100MB+) #19580

• 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

[welcome]

First PR! 🚀 We sincerely appreciate that you have taken the time to propose a change to AnkiDroid! Please have patience with us as we are all volunteers - we will get to this as soon as possible.

[github-actions]

Important

Maintainers: This PR contains Strings changes

1. Sync Translations before merging this PR and wait for the action to complete
2. Review and merge the auto-generated PR in order to sync all user-submitted translations
3. Sync Translations again and merge the PR so the huge automated string changes caused by merging this PR are by themselves and easy to review

[david-allison]

Use the .show extension

[ujjol1234]

Done

[ujjol1234]

Hi @david-allison, I have implemented your suggested changes. Could you please check them out?

[david-allison]

Quick review on my phone, I think this is almost there. Thanks!!

[ujjol1234]

Hi @david-allison, hope you are doing well!
Could you review the new changes I have made?

[david-allison]

Cheers! Sorry for the delay. Also needs a de-conflcit

[david-allison]

Suggested change

	Timber.e(e, "Failed to add large media file after warning")
	Timber.w(e, "Failed to add large media file after warning")

[ujjol1234]

Hi @david-allison I have made the required changed, could you please review them?

[david-allison]

Suggested change

// Initial call checks size (skipSizeCheck = false)

[david-allison]

It doesn't make sense to me that we continue execution if the file is null.

I may have missed something

[david-allison]

Suggested change

// Initial call checks size (skipSizeCheck = false)

[david-allison]

This is great!

I think removing the null check will massively improve typing throughout the change

Optional extension: define a value class for something like fileSize to produce a nicer looking string format

Here's something similar I wrote last night which might be of use

@JvmInline
value class Bytes(val bytes: Long) {
    fun toShortString(context: Context): String = Formatter.formatShortFileSize(context, this.bytes)
}

val Int.bytes get() = Bytes(this.toLong())

[ujjol1234]

You are absolutely right @david-allison. I see now how removing the null check significantly cleaned up the types in both the exception class and the fragment. Also, that Bytes value class is super helpful. I have implemented it as you shared.