fix(cli): merge config based on the first one

[Legend-Master]

Fix #13114

Fix the behavior change from #12970

[github-actions]

Package Changes Through 357912c

There are 6 changes which include @tauri-apps/api with patch, tauri-bundler with patch, tauri-cli with minor, tauri with minor, tauri-utils with minor, @tauri-apps/cli with minor

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
@tauri-apps/api	2.4.0	2.4.1
tauri-utils	2.3.0	2.4.0
tauri-bundler	2.3.0	2.3.1
tauri-runtime	2.5.0	2.5.1
tauri-runtime-wry	2.5.0	2.5.1
tauri-codegen	2.1.0	2.1.1
tauri-macros	2.1.0	2.1.1
tauri-plugin	2.1.0	2.1.1
tauri-build	2.1.0	2.1.1
tauri	2.4.0	2.5.0
@tauri-apps/cli	2.4.0	2.5.0
tauri-cli	2.4.0	2.5.0

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[anatawa12]

New behavior in this PR looks unable to remove key with second / later -c option which is inconvenient and inconsistent I think.

When we divide -c '{"version":"1.0.2-beta.0", "bundle":{"windows":{"certificateThumbprint": null}}}' to -c '{"bundle":{"windows":{"certificateThumbprint": null}}}' -c '{"version":"1.0.2-beta.0"}' works but to -c '{"version":"1.0.2-beta.0"}' -c '{"bundle":{"windows":{"certificateThumbprint": null}}}' does not work as expected, which is unexpected to me.

Is there any reason to merge -c options into one then merge, instead of merge to original config one by one?

[Legend-Master]

We need to store it in the TAURI_CONFIG environment variable and pass it to codegen and tauri-build, that's why it's merged together first I think

I don't know if changing it to a vector of merge configs would be breaking or not, or we could change the way we pre-merge the configs? Like instead of removing the value, we preserve them as null