🎨 Standardize naming for atlases used in RBC

[shnizzedy]

Fixes

Related to FCP-INDI/C-PAC_templates#4, #1641, & #1808 by @shnizzedy
With #1825, this PR is fully included in #1831, so if all three are approved, we can just merge #1831 and get all three without having to do any merge conflict resolution.

Description

For the atlases used in rbc-options,

• adds the atlases to CPAC/resources/templates/BIDS_identifiers.tsv
• replaces f'atlas-{strip_extension(basename(atlas_filename))}' with f'atlas-{atlasname}' or f'atlas-{atlasname}_desc-{atlasdesc}' in derivative filenames
  (for example,

  sub-NDARYX806FL1_ses-HBNsiteRU_task-rest_run-1_atlas-Schaefer2018space-FSLMNI152res-2mmdesc-1000Parcels17NetworksOrder_desc-Mean-1_timeseries.1D
  

  becomes

  sub-NDARYX806FL1_ses-HBNsiteRU_task-rest_run-1_atlas-Schaefer2018_desc-1000p17_desc-Mean-1_timeseries.1D`
  

  )

Technical details

This still allows duplicate desc entities and -s in entity values; those will be addressed in separate PRs

Screenshots

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the develop branch of the repository.
• My commit messages follow best practices.
• 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).
• I tried running the project locally and verified that there are no visible errors

Developer Certificate of Origin

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.