Implement a new configuration merging logic

[imobachgs]

Problem

In the new API, when merging collections (e.g., a Vec), both of them are merged together. For instance, if you send a PATCH with a list of patterns for installation, it would add them to the existing list.

The way to reset the list of patterns is to use PUT, but it forces to send the whole configuration.

The reason for this behavior is that we rely on merge_struct for merging the configuration. It was kind of an urgent solution, but we might need to search for a better alternative (or implement our own).

Solution

Replace the whole list, so we can add, update, and remove elements using a PATCH request. It uses the merge crate. When reviewing the code, take into account that when calling the merge function, the receiver is the configuration to update, while the argument to this function is the original one.

config.update(original);

Notes

Most of the unit tests are generated by Gemini, although some minimal changes were required.

Open question

• How to proceed in the storage section?

[jreidinger]

so it means, if I intentionally send empty list of files, it won't be overwritten and instead it will keep old list of files? I find this strange.

[imobachgs]

Yes, I think it is wrong. But IMHO the real problem is that we should use an Option here too. Otherwise, you cannot differentiate when you want to reset the list.

[jreidinger]

I miss tests for files case.

[jreidinger]

I would avoid having this on one line, is possible to have it on two?

[jreidinger]

and question is also here how it will behave when I send intentionally empty list of network connections, will it overwrite or not?

[imobachgs]

No, I left the formatting to rustfmt and it does it in this way.

[jreidinger]

and this exactly show why I do not think that overwrite_empty is good one for arrays as it means, that you cannot set intentionally empty list.