Extracting creates a directory even when not needed

Extracting archives from the context menu (three dots) causes Material Files to create a separate directory in the target location (presumably for tarbomb protection), even if there's only file (plain or directory) in the archive. This behavior can be confusing to users (have had a confused user report this to me).

Reproducing

1. Download the examples onto your device.

   • single_file.zip: Contains a single file named foo
   • single_dir.zip: Contains a single directory named foo, which contains files foo and bar.

   As you can see, neither example is a tarbomb.

2. In Material Files, open the context menu for each and extract them somewhere.

Observed behavior

The following directory structure for extracted single_file.zip:

• single_file (directory)
  • foo

The following directory structure for extracted single_dir.zip:

• single_dir (directory)
  • foo (directory)
    • foo
    • bar

Expected behavior

The following directory structure for extracted single_file.zip:

• foo

The following directory structure for extracted single_dir.zip:

• foo (directory)
  • foo
  • bar

For actual tarbombs, the behavior should remain as it is.

Start at the context-menu extraction flow and reproduce the behavior with the supplied single_file.zip and single_dir.zip examples. Compare extraction handling for archives with one top-level file or directory against actual tarbombs; done means the two examples extract directly while tarbomb protection remains unchanged.