added acq_details options - #211

I have two rather substantial PRs ready to go after this (one includes modification of all the modeling modules, and the other is a half-dozen new modules to implement motion scrubbing).

At first I though submitting these as three smaller PR was a good approach (hence this one-file PR of our BIDS tweaks) but in hindsight maybe this is a bad idea? It occurs to me I might be tripling the number of times the test suite has to get run.

If there's a consensus that one big PR would make testing easier, I could do that instead.

Any thoughts?
Mike

Although, there are some practicality in submitting one PR, I also think independent substantial changes deserve separate PRs.
If these changes affect well-defined areas in the code and well-specified use-cases, then we can test them separately - even in parallel.

I can see a few useful settings, however, it is not clear from the beginning what are the default settings. Since they are not part of the app_paremetersets. I can also see that backward compatibility is ensured by using isfield(...), you may be able to hit two birds with one stone, if you would define defaults settings at the beginning (and in one place), if they are not specified. Similarly to

Okay, I added initialization that hopefully clarifies the defaults.

Tested locally; all looks good on my end...