🐛 Sparsity thresholds not scaling for network centrality

[shnizzedy]

Describe the bug

Updated string parameters from	to
[…]	[…]
'sparsity'	'Sparsity threshold'

― https://github.com/FCP-INDI/C-PAC/pull/1396

https://github.com/FCP-INDI/C-PAC/blob/a8928461adc3dfc5c15b2aee6ead5be1bec54eca/CPAC/pipeline/schema.py#L83-L84

"sparsity" isn't a valid "threshold_option" since < 1.8.0, but that's the value used to scale the threshold value

https://github.com/FCP-INDI/C-PAC/blob/a0e425dd66a51743452c42b0c17c4ba24c38e3b0/CPAC/network_centrality/pipeline.py#L47-L49 https://github.com/FCP-INDI/C-PAC/blob/3facedbfbc81e581e556baf280b3421d76622e6c/CPAC/network_centrality/network_centrality.py#L72-L73

Expected behavior

The scaling occurs for 'Sparsity threshold' instead of for 'sparsity' or the threshold range is 0 ‒ 100 instead of 0 ‒ 1 for 'Sparsity threshold'

Acceptance criteria

• [ ] The scaling occurs for 'Sparsity threshold' instead of for 'sparsity' or
• [ ] the threshold range is 0 ‒ 100 instead of 0 ‒ 1 for 'Sparsity threshold'

C-PAC version

1.8.0 ‒ 1.8.5

Additional context

Discovered while working on https://github.com/FCP-INDI/C-PAC/pull/1998

[shnizzedy]

[shnizzedy]

Fixed in 1.8.6