Add new Tests and Demos for additional MASWE-0006 issues

[cpholguera]

@cpholguera

I agree. You can add new tests for "MASWE-0006: Sensitive Data Stored Unencrypted in Private Storage Locations".

For example, the new test we'd need here could have this metadata:

---
platform: android
title: SharedPreferences API Storing Sensitive Data Unencrypted in the App Sandbox
id: MASTG-TEST-02xx
type: [dynamic]
weakness: MASWE-0006
profiles: [L2]
---

And then, in separate PRs, you could add:

---
platform: android
title: DataStore API Storing Sensitive Data Unencrypted in the App Sandbox
id: MASTG-TEST-02xx
type: [dynamic]
weakness: MASWE-0006
profiles: [L2]
---

etc.

Important: each Overview should detail the specific locations and APIs, always linking to the corresponding MASTG-KNOW component, for example:

• Shared Preferences -> TODO: assign the new MASTG-KNOW ID
• MediaStore API -> TODO: find the new MASTG-KNOW ID

Note: These items are currently in https://mas.owasp.org/MASTG/knowledge/android/MASVS-STORAGE/MASTG-KNOW-0042/ but this could be split into different articles with unique IDs.

@bernhste

Makes sense: I will write Tests and Demos for

1. App Writing Sensitive Data to Sandbox using SharedPreferences
2. App Writing Sensitive Data to Sandbox using DataStore
3. App Writing Sensitive Data to Sandbox using Room
4. App Writing Sensitive Data to Sandbox using SQLite

There is already a Demos for:

1. App Writing Sensitive Data to World Readable External Storage (MASTG-DEMO-0005)
2. App Writing Sensitive Data to Sandboxed External Location (MASTG-DEMO-0004)
3. App Writing Sensitive Data to World Readable External Location (MASTG-DEMO-0003)

I will start with the tests, but would wait for some feedback after the first PR.

Originally posted by @bernhste in #3359 (comment)

[bernhste]

To keep the issues smaller, I created three different ones. I suggest, we track it there and close this one.