Improve archive extraction path error handling

[andrewfrench]

The Problem/Issue/Bug:

The review in #994 describes some issues with import-files, namely one where a bad extraction path would return a success despite having extracted zero files into the project.

Additionally, a regression was identified where a user would no longer be prompted for an archive extraction path when using the import-files interactive mode.

How this PR Solves The Problem:

If no files match the extraction path in an archive, an error is returned to the user.

The interactive extraction path regression was fixed as well.

Manual Testing Instructions:

Provide an archive in interactive mode and ensure the extraction path prompt is presented.

Provide an invalid extraction dir and ensure an error is generated.

Automated Testing Overview:

Related Issue Link(s):

#944

[rickmanelius]

I still note a regression. Here's my testing pattern:

• Interact Mode
  • PASS: Incorrect file: Errors out correctly
  • PASS: No extract path: Imports entire archive correctly
  • PASS: Correct file and extract path: Imports correctly
• Flag Mode
  • PASS: Incorrect file: Errors out correctly
  • FAIL: No extract path: Claims imported but it doesn't.
  • PASS: Correct file and extract path: Imports correctly

To note, here was the command I used to get the false positive: ddev import-files --src db.20180815_104847.tar.gz

[rickmanelius]

After a screen share and retest with @andrewfrench, it appears that it was a testing error on my side. I must have been validating against a different directory with an empty repo for that one test. We tested each scenario again and we passed.

[rfay]

Ooops, I get No upload directory has been specified for the project type drupal6 on a d6 site - that's doing it from just ddev import-files with no flags

[rfay]

Cancel that. I had wrong ddev. quicksprint installed a new one for me!

[rfay]

A modest amount of testing and scan through the code ran into no problems although I learned about the difference between archives with ./

structure and straight structure. I think ./ is more likely; we'll deal with this in the future if it comes up.