Android Device D2D: Map and analyze a file system

A file system is like a rootfs so we should reuse the steps to analyze these.
On top of this there is a specific layout to Android filesystem trees with specific temp and config files that we need to account and possibly ignore.
The d2d of one filesystem would go through these specific steps beyond :
- [ ] Android Device D2D: Ignore Android-specific ignorable temp and config files
- [ ] Android Device D2D: Decompile/collect symbols and map native binaries (not in an APK) to source code. We likely will reuse most of the APK code. See:
- https://github.com/aboutcode-org/scancode.io/issues/1375
- [ ] Android Device D2D: collect symbols and map Dalvik/VM classes.dex bytecode and similar (not in an APK) to source code. We should reuse the same steps as for an APK
- https://github.com/aboutcode-org/scancode.io/issues/1372
- https://github.com/aboutcode-org/scancode.io/issues/1373