Bug: using yaml.v2 for deserialization may lead to failure in json serialization

[liu-hm19]

What happened?

Since the Env in Container of the Workload is the type of MapSlice, which only exists in yaml.v2 package, currently we use yaml.v2 for unmarshaling module resources. But it does not support the nested map[string]interface{}, resulting it become map[interface{}]interface{}, which may easily cause the subsequent JSON marshaling to fail because JSON keys can only be the type of string.

Here is a related discussion on GitHub: go-yaml/yaml#139

What did you expect to happen?

Please unify the usage of yaml.v2 & yaml.v3. For me, better to use yaml.v3.

How can we reproduce it (as minimally and precisely as possible)?

Execute kusion build, kusion preview, kusion apply or kusion destroy on Kusion module with nested map[string]interface{} config.

Anything else we need to know?

No response

Kusion version

$ kusion version
# paste output here

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools