Storing freesurfer's outputs in a semi-BIDS-appropriate structure

[GalKepler]

To allow an adequate level of robustness in freesurfer's derivatives' post-processing, it would be helpful if they were stores in a semi-BIDS manner.
Maybe something like this:

• freesurfer
  • sub-<participant_label>
    • ses-<session_id>
      • <input T1w image's name>
      • ...
    • ...