Update 0x05d-Testing-Data-Storage: Internal Storage, External Storage incl. Scoped Storage, APIs and permissions

[cpholguera]

This pull request updates Document/0x05d-Testing-Data-Storage.md file, focusing on improving the guidance for handling data storage on Android. The changes include replacing Java examples with Kotlin, expanding on internal and external storage security practices, and updating information on scoped storage and related permissions.

Key changes:

Internal Storage:

• Replaced Java code snippet with a Kotlin example for storing sensitive information in internal storage.
• Added guidelines to ensure proper file access modes and referenced Android Security Guidelines.

External Storage:

• Expanded the section on external storage to include risks, security guidelines, and best practices.
• Detailed the use of scoped storage, including how to opt-out and permissions required for accessing media files.
• Provided examples of querying the MediaStore and handling permissions for accessing external storage.

MediaStore API:

• Introduced the MediaStore API section, explaining how to interact with media and non-media files and the permissions required for different Android versions.

Manifest Permissions:

• Updated and detailed the permissions required for accessing external storage, including READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE, and MANAGE_EXTERNAL_STORAGE.
• Explained the new permissions READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, and READ_MEDIA_AUDIO introduced in Android 13.

[serek8]

I left only one optional suggestion

[serek8]

Good example. I can't tell for Android devs but wouldn't an example with getExternalFilesDir be easier here?

[cpholguera]

Please post a suggestion with that case as well, we can have both but wanted to definitely highlight this

[serek8]

I wanted to suggest the following:

Suggested change

	For example, trying to access a file stored using the `MediaStore` API with a `content://` URI like `content://media/external_primary` would only work as long as the image _belongs_ to the invoking app (due to `owner_package_name` attribute in the `MediaStore`). If the app calls a `content://` URI that does not belong to the app, it will fail with a `SecurityException`:
	For example, if you create a file within the external storage in the following way:
	```kotlin
	val path = Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_PICTURES);
	val file = File(path, "image.jpg");
	FileOutputStream(file).use {
	bitmap.compress(Bitmap.CompressFormat.JPEG, 100, it)
	}
	Accessing this image would only work as long as the image belongs to the invoking app.

But now when I think of it, the app would require WRITE_EXTERNAL_STORAGE, which isn't possible anymore. I believe that the current example fits just right.