Issues with ELF d2d on Debian debug package

I run an ELF d2d with
- http://deb.debian.org/debian/pool/main/b/binutils/binutils_2.31.1.orig.tar.xz#from
- http://ftp.us.debian.org/debian/pool/main/b/binutils/libbinutils-dbg_2.31.1-16_amd64.deb#to

There are a few issues:
- [ ] https://github.com/nexB/scancode.io/issues/1215
- [ ] https://github.com/nexB/purldb/issues/422 which leads to an incorrect purldb match ofn a random deb package in PurlDB
- [ ] Extracted to/ .deb package is not detected as a package (to/control.tar.xz-extract/control)
- [ ] to/data.tar.xz-extract/usr/lib/debug/.dwz/x86_64-linux-gnu/libbinutils.debug has some unmapped paths. We should report these are "require-review"
- [ ] Some paths not mapped may need to be skipped?
- dwarf_included_paths_not_mapped:
- `build/binutils-lybw70/binutils-2.31.1/builddir-single/opcodes/`
- generally things that come from the standard library are likely best skipped by default?
- [ ] Determine if file built in an ELF comes from a C/C++ standard library
- Files like `usr/include/errno.h` or `usr/include/x86_64-linux-gnu/bits/setjmp.h`