Prefer list to dictionary in configuration for multi-items.

[YooSunYoung]

Background Reason

1. To prevent overwriting by having same keys on different items, so that we can handle those cases.
2. To have intuitive field called name in the configuration chunk of each item (workflow or target or application).

At the beginning, when you have multiple items in the field, I tried to write them as dictionaries.
For example, workflow configuration was written like below.

data-reduction:
    workflows:
        workflow-name-1:
            ...
        workflow-name-2:
            ...

But one day I made a mistake to use the same name twice for different target and then the second one just overwrites it and pyyaml doesn't really tell you.

Another annoying thing is when you want to map a function over all the items in the workflows or targets, you might want to use the name, which used to be the key.
You can also just map over dict.items(), for me it was more straightforward to have the name as a field of each item-dictionary, not as a separate variable.

So I made all configuration fields that has multiple items as list rather than dict and each item has name field that represents the name.

Now it looks like this:

data-reduction:
    workflows:
       - name: workflow-name-1
         process: ...
         ...
       - name: workflow-name-2
         process: ...
         ...

Pros

By this way, we can also avoid checking if it is a list or a dictionary since it will always be lists.

Cons

You can't directly access to the item you want by name.
So in the data-reduction application module, it makes a dictionary out of the list first and then use the name as the key.
The overwriting error raise should be implemented.