Prevent Nipype from emitting .proc-* files to user working dir Fix #1955

Fixes

Fixes #1955 by @amygutierrez

Description

Since Nipype version ~1.8.x Nipype emits many (!) .proc-* to the user working directory (wherever the user started nipype from, instead of nipype working directory node subdirectories)

Technical details

@shnizzedy 's exhaustive internal writedown 🕵️

C-PAC and fMRIPrep both hit the issue upgrading from nipype 1.5.x to 1.8.x; I think this chdir that used to be before initializing the ResourceMonitor led to this relative path being inside the relevant subdirectory of the working directory, but now it's initialized without changing directories first

The relevant nipype BaseInterface is now monkey patched to use the individual node workdir to emit .proc-* files to
This means they will automatically be cleaned if the working dir is not retained (no --save-work-dir)

Tests

Screenshots

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the develop branch of the repository.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added tests for the changes I made (if applicable).
[ ] I updated the changelog.
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

``` Developer Certificate of Origin Version 1.1 Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 1 Letterman Drive Suite D4700 San Francisco, CA, 94129 Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. ```

FCP-INDI / C-PAC