Bug: CLI for node level secrets not applying to a specific node

[dlarson04]

Describe the bug.

Trying to add a node level secret using the CLI

# hzn sm secret add --secretKey test_node --secretDetail 12345   /user/larsond/my-new-test-secret --nodeId=test-node  --overwrite
Secret "/user/larsond/my-new-test-secret" successfully added to the secrets manager.
# hzn sm secret read  /user/larsond/my-new-test-secret   <- This should have failed
{
  "key": "test_node",
  "value": "12345"
}
# hzn sm secret read  /user/larsond/my-new-test-secret --nodeId=test-node <- This correctly succeeds
{
  "key": "test_node",
  "value": "12345"
}
# hzn sm secret read  /user/larsond/my-new-test-secret --nodeId=test-node44 <- This should have failed
{
  "key": "test_node",
  "value": "12345"
}

Also seeing

# hzn sm secret read  user/larsond/my-node-test-secret --nodeId=test-node101
Error: No secret(s) found under secret name "user/larsondnode/test-node101/my-node-test-secret"  <- this have a `/` between `larsond` and `node`
# hzn sm secret read  /user/larsond/my-node-test-secret --nodeId=test-node101  <- Not sure why this didn't honor the nodeId
Error: No secret(s) found under secret name "user/larsond/my-node-test-secret"

Describe the steps to reproduce the behavior.

No response

Expected behavior.

No response

Screenshots.

No response

Operating Environment

Linux

Additional Information

No response

[dlarson04]

verified in 2.31.0-1450