fix: check_and_call_extract_file uses the first matching method and options, instead of the first matching method and last matching options

[jpmckinney]

Otherwise, if I want to use a different method for one file AND use options, I can't do, for example:

[myextractor: path/file.py]
myoption = myvalue

[python: path/**.py]

The current code will match path/file.py to myextractor, but it'll use the empty options from python...

[akx]

LGTM, but could you add a test for this? Thanks!

[jpmckinney]

I would love to, but it's very hard to figure out where/how to test this. Basically, I'd need some scaffolding to be able to provide a configuration file, source files and a custom extractor and test whether the output is as expected.