Okdata-cli

* Fix previous release (the new `skatteetaten:testnorge/testdata.read` scope was
not included).

* New command `datasets create-pipeline` for creating pipelines for existing
datasets.
* The dataset creation wizard can now create event type datasets. The database
dataset type has been removed.
* More robust dataset/version/edition URI parsing.
* Added new scope for skatteetaten:testnorge/testdata.read.

* New commands `okdata -e` and `okdata -v` for printing the current environment
and the current version of okdata-cli, respectively.
* The default choice for dataset visibility is now non-public (red). Also warn
when a dataset is about to be registered as public (green).

* The minimum required version of `okdata-sdk` is now 3.1.1. This ensures
compatibility with a much newer version of `python-keycloak`, eliminating
reliance on certain vulnerable dependencies.
* Added support for creating JSON->Delta dataset pipelines.
* The dataset creation wizard has been simplified (it no longer asks
about geodata details, standards conformity and contact phone
number).

* The `okdata pubreg` family of commands has been renamed to `okdata pubs` (for
"public services") to reflect that they now don't only handle Maskinporten
clients, but also ID-porten clients.
* Added support for creating CSV->Delta dataset pipelines.
* Added a shorthand for granting a user all permissions on a resource by not
specifying the `scope` parameter to the `permissions add` command, similar to
the way `permissions rm` works.
* Fixed extraneous newline printing in table output.
* Improved error messages in the `datasets ls` and `datasets cp` commands when a
given dataset doesn't exist.

* The `okdata status` command can now be set to watch the status of a dataset
upload with the `--watch` option.
* The `datasets ls` command now accepts a single optional URI argument that can
denote either a dataset, version, or edition:

- `okdata datasets ls {dataset_id}`
- `okdata datasets ls {dataset_id}/{version}`
- `okdata datasets ls {dataset_id}/{version}/{edition}`

* Automatically created editions now get timestamped correctly. Previously it
was assumed that the user always operated in UTC+2.