Should we stick to cbrain UI labels, internal model names or both

[MontrealSergiy]

CBRAIN UI uses projects instead of group, version instead of tool config.

Which ones should we use in CLI?

Presently command is project, but filter is group_id

@prioux @dlq @natacha-beck

[sanchalitorpe-source]

I worked on aligning the CLI terminology with the CBRAIN UI labels.

Changes made:

• Replaced CLI arguments using group_id / --group-id with project_id / --project-id.
• Updated related help messages to use Project ID instead of Group ID.
• Backend API calls still use /groups to remain compatible with the existing CBRAIN API.

This keeps the CLI consistent with the CBRAIN UI while preserving the internal model naming where required.

Happy to adjust if you would prefer a different approach (e.g., supporting both names for backward compatibility).