[FEATURE] Better management of DTaaS CLI configuration

[prasadtalasila]

Describe the feature

As an admin I want to start with single pip package So That no separate zip file is needed for managing users.

Describe the problems your feature request solves

The current installation package gives the following files to the user.

cli/
  README.md
  README.pdf
  dtaas.toml
  user.local.yml
  user.server.yml
  user.server.secure.yml

Since users (usually) do not change the docker compose files, there is no point in giving them in this directory.

Describe the solution you'd like

It would be ideal to not give this directory at all during the software release. Users can directly use the CLI to make the necessary installation. The CLI can also generate the required dtaas.toml file.

The following additional subcommands need to be added to the DTaaS CLI.

Manage config file with

dtaas admin config generate [--output FILE]
dtaas admin config validate [FILE]
dtaas admin config show

The client, compose, forward-auth, service configs need to be generated and validated.

Additional context

The dtaas.toml config file needs to be extended with the following additional fields

[common.security]
https=true # default value, but can be set to false
public_key=/home/Desktop/DTaaS/certs/fullchain.pem
private_key=/home/Desktop/DTaaS/certs/privkey.pem
# add sample paths for Windows OS

Success Criterion

Checklist:

• The user management happens with only dtaas.toml
• Sample dtaas.toml is generated for user
• Docker compose files are not distributed to users
• Documentation is updated
• No qlty issues