databases: support displaying URI and Created in list with format flag

[andrewsomething]

In order to make the default display of doctl databases list legible in a terminal, it does not display all attributes. To achieve this, the Databases.Cols() displays different columns if Databases.Short = true. It is false when generating help output. So columns not shown are indicated as available as format options. Exposing those to Databases.ColMap() regardless of whether the sort version is used allows them to be used with the format flag while still retaining the default behavior for the list view.

Before this change, running the following command would error:

$ doctl databases list --format ID,Name,Engine,Version,URI,Created
Error: unknown column "URI"

Now it should successfully display the given fields.

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
15175723	Triggered	PostgreSQL Credentials	fc58239	integration/database_list_test.go	View secret
15175724	Triggered	MySQL Credentials	fc58239	integration/database_list_test.go	View secret
15175725	Triggered	MySQL Credentials	fc58239	integration/database_list_test.go	View secret
15175726	Triggered	PostgreSQL Credentials	fc58239	integration/database_list_test.go	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[loosla]

🔥 Thanks Andrew