Add motion and emg datatypes

[JoeZiminski]

This PR extends the narrow datatypes to include motion and emg, as per NeuroBlueprint PRs #67 and #68.

It required extending the backwards-compatibility checking for the TUI arguments, to fill-in the settings for missing datatypes. In general, the narrow-datatype machinery is not very extensible, this should be addressed in issue #516.

[cs7-shrey]

a subtle bug here. it should probably be something

    is_not_missing_narrow_datatypes = all(
        [
            dtype in user_settings["tui"]["create_checkboxes_on"]
            for dtype in all_narrow_datatypes
        ]
    )

if we're checking for all narrow datatype to be present in user_settings

[cs7-shrey]

same here

[cs7-shrey]

I am not sure but atm, this can break things now especially when we're adding more narrow datatypes. There are going to be cases which although use the newer version of datashuttle i.e has_narrow_datatypes is True but is_not_missing_narrow_datatypes is False (because of "motion" and "emg"), in that case, user_settings["tui"]["transfer_checkboxes_on"][key] is still a dict but we're assigning it to a boolean value, new_transfer_checkbox_configs[key]["on"]

So, I'm assuming the has_narrow_datatypes flag can provide us enough information about where user_settings["tui"]["transfer_checkboxes_on"][key] is a dict (newer datashuttle version ) or not (older datashuttle version). We can then do the assignment according to the flag.

[cs7-shrey]

If this part of the code is intended to copy the user_settings' narow datatypes config to the new_create_checkbox_configs, we should probably do it something like

for narrow_datatype in all_narrow_datatypes:
    if (
        narrow_datatype
        in user_settings["tui"]["create_checkboxes_on"].keys()
    ):
        new_create_checkbox_configs[narrow_datatype] = user_settings["tui"][
            "create_checkboxes_on"
        ][narrow_datatype]

same we can do for transfer_checkboxes_on below and at the end we can do

user_settings["tui"]["create_checkboxes_on"] = new_create_checkbox_configs
user_settings["tui"]["transfer_checkboxes_on"] = new_transfer_checkbox_configs

This will both maintain the order of key-value pairs in the settings and also ensure that previously set settings are respected.