--set-literal does not allow backslash escaping in NAME

[anbrsap]

Problem

Helm option --set-literal does not perform backslash escaping for value names.

Example: --set-literal 'a.b\.b\.b.c=x,\[]{}x' has the same effect as using the following values file:

a:
  b\\:
    b\\:
      b:
        c: 'x,\[]{}x'

This does not make any sense, because it prevents setting values with special characters in the name.

Expected Behavior

--set-literal should allow to set values whose name contains characters with special meanings in a path (e.g. . or [) using the same backslash escaping rules as used for other ---set* options.

Example: --set-literal 'a.b\.b\.b.c=x,\[]{}x' should have the same effect as using the following values file:

a:
  b.b.b:
    c: 'x,\[]{}x'

Additional Info

Output of helm version:

version.BuildInfo{Version:"v3.14.4", GitCommit:"81c902a123462fd4052bc5e9aa9c513c4c8fc142", GitTreeState:"clean", GoVersion:"go1.21.9"}

[gjenkins8]

If --set-literal 'a.b\.b\.b.c={}' behaves differently to e.g. --set-json 'a.b.b.b.c={}' for the key set. Then yeah, this seems like a bug (but it might be hard to change the existing behavior without backwards compatibility concerns)