Use mem_mb instead of mem_gb

[smeisler]

Closes none, but discussion on slack channel.

Changes proposed in this pull request

Use mem_mb in command line instead of gigabytes.

More consistent with other apps, allows the slurm memory environment variable to be directly input, which is helpful for BABS.

Documentation that should be reviewed

[smeisler]

I thought the easiest route would be to change the CLI argument and then update from mb to gb in config so everything else can stay the same.

[tsalo]

It looks like fMRIPrep does it all in the CLI:

    g_perfm.add_argument(
        '--mem',
        '--mem_mb',
        '--mem-mb',
        dest='memory_gb',
        action='store',
        type=_to_gb,
        metavar='MEMORY_MB',
        help='Upper bound memory limit for fMRIPrep processes',
    )

[smeisler]

Changed it to be more fmriprep-like

[codecov]

Codecov Report

Attention: Patch coverage is 20.00000% with 4 lines in your changes missing coverage. Please review.

Project coverage is 79.02%. Comparing base (d43d167) to head (d373ad2).

Files with missing lines	Patch %	Lines
xcp_d/cli/parser_utils.py	20.00%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1417      +/-   ##
==========================================
- Coverage   79.06%   79.02%   -0.05%     
==========================================
  Files          58       58              
  Lines        7347     7352       +5     
  Branches      970      970              
==========================================
+ Hits         5809     5810       +1     
- Misses       1256     1260       +4     
  Partials      282      282              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.