🚸 Make specialCasings [more] comprehensive

[shnizzedy]

Related problem
Related to #66, #76

Proposed feature

• go through all the keys in default_pipeline.yml and add any exceptions not yet covered to the specialCasings dictionary
• rename the variable specialCasings
• add a step to developer documentation to add to this dictionary if adding/changing a key that won't already be handled correctly

Additional context
The labels in the GUI are derived from the keys in default_pipeline.yml by replacing _s with spaces and Title-Casing each word not in

C-PAC_GUI/app/containers/pipeline/parts/PipelinePart.jsx

Line 36 in c7e4e18

const keepLower = ["at", "of", "per", "to"] // words to not capitalize

As I was working on #76, I made a dictionary of exceptions to expand differently:

C-PAC_GUI/app/containers/pipeline/parts/PipelinePart.jsx

Lines 22 to 35 in c7e4e18

	const specialCasings = {
	afni: "AFNI",
	ants: "ANTs",
	freesurfer: "FreeSurfer",
	fsl: "FSL",
	acpc: "ACPC",
	aroma: "AROMA",
	bet: "BET",
	dir: "Directory",
	epi: "EPI",
	nlmf: "NLMF",
	roi: "Region of Interest",
	tse: "Timeseries Extraction",
	}; // words with special casing or adjusted spelling

but I was not at all comprehensive. I just added items to that list as I noticed miscapitalized (at first just that, hence the name specialCasings) or ambiguous labels.