generalize usage of intended_for field where applicable and dependency sub-structure

[Remi-Gau]

• generalize usage of intended_for field where applicable and dependency sub-structure

Originally posted by @Remi-Gau in #124 (comment)

For the in the intended for, it should at least cover fmaps, m0scan and similar files that have an intended for in their metadata

For dependencies (tempted to call it informed by as pybids does it), it could be more flexible and could / should include events.tsv files for any "task" file for example.