feat: training only allow dataset name

[ypang-neuraco]

Features

• Remove dataset ID as input from training runs

Expected behaviour

• Dataset name unique within org
• User's own dataset can share the same name with shared dataset
• When selecting dataset for training, prioritise user's dataset in org over shared dataset. Fall back to shared dataset if no matching dataset found in org

Items

• NCRL-170

[github-actions]

✅ PR source branch is valid

• Source: feat/training-only-allow-dataset-name
• Target: develop

[github-actions]

Consider updating changelogs/pending-changelog.md with a summary of this change for the release notes. This is optional and non-blocking.

[kwangneuraco]

Hi i just give a bit more context, there are several concerns regarding this change: (1) please make sure dataset name is uniquely linked to one dataset id, and after the change of the dataset name, it is still valid.
(2) Before we had a concern that dataset maybe shared between different organizations, and the dataset name may conflict with some private ones, how this can be handled?
Maybe we should talk with @CougarTasker before proceed with it :)

[ypang-neuraco]

Hi i just give a bit more context, there are several concerns regarding this change: (1) please make sure dataset name is uniquely linked to one dataset id, and after the change of the dataset name, it is still valid. (2) Before we had a concern that dataset maybe shared between different organizations, and the dataset name may conflict with some private ones, how this can be handled? Maybe we should talk with @CougarTasker before proceed with it :)

(1) From what I understand, when creating datasets the name is checked against other dataset names within the organisation so the dataset name should be unique within the organisation. When selecting dataset by name, we only search within the organisation so one dataset name should only map to one dataset ID. Additionally, users are not allowed to rename a dataset to be the same name as another dataset within the organisation. I haven't checked what happens after renaming so I will try that and come back to you.

(2) I don't have the context on this but I think if datasets were to be shared between organisations, and there is a conflict in the name, at that point we can ask the user to rename the dataset.