Misleading output of publish setup when pgp keys stored in config

[MaciejG604]

Version(s)
Scala CLI version: 0.2.0
Scala version (default): 3.2.2

Describe the bug
When using the publish setup subcommand all the parameters get written to publish-conf.scala except publish.secretKey and publish.secretKey if they reside in config (which is sensible since using directives don't support "config:..."). But the output of the subcommand is as follows:

(the subcommand is run for the second time so the default values are almost all there except pgp values)

1 option needs to be set
  pgp-secret-key


Wrote ./publish-conf.scala

Project is ready for publishing!
To publish your project, run
  scala-cli publish .

But in fact nothing is written to ./publish-conf.scala and running scala-cli publish . results in artifacts not getting signed which is mandatory for publishing to Sonatype repo ("central-s01").
So correct command in this case is

scala-cli publish  \
  --secret-key config:pgp.secret-key \
  --secret-key-password config:pgp.secret-key-password .

as in documentation.

To Reproduce
clone a github project and use commands:

scala-cli config --create-pgp-key
scala-cli config publish.credentials s01.oss.sonatype.org env:SONATYPE_USER env:SONATYPE_PASSWORD
scala-cli publish setup .

Expected behaviour
The publish setup should take care of everything so using directives should support "config:..." or a proper output shudl be provided given user stores pgp keys in config:

1 option needs to be set
  pgp-secret-key


Values for pgp-secret-key and pgp-secret-password found in config.

Project is ready for publishing!
To publish your project, run
  scala-cli publish  \
    --secret-key config:pgp.secret-key \
    --secret-key-password config:pgp.secret-key-password .