implement --db-username, --db-password and --save-db-password to the publish command for wallet embedded credentials

[ckchuaa]

We are not sure if these arguements are implemented as there is discrepancy between v2.0.8 release note and the tabcmd2 cmd page.

We are currently using tabcmd2 v2.0.11 on red hat 8.6 but we are not able to embed credential when publishing extracted data sources.

--db-username and --db-password cannot change the actual username password.
--save-db-password cannot embed credentials.
--db-password does not accept empty input ("") and return error 400000: Bad Request Payload is either malformed or incomplete.
when I set --db-username and --db-password to dummy value with --save-db-password, the data source is marked as embedded password on server side but the password is wrong.

We hope tabcmd2 can support this feature to enable passwordless deployment for sources using wallet connection.

[mandalmanas786]

Please look into this issue on prority we are facing similar issue and our automated deployment getting blocked