Take decision on whether / how the nexus-python-sdk checks Nexus API specific constraints

This is feedback provided after a first usage of the nexus-python-sdk and its documentation to perform basic operations in a Nexus V1 deployment.

Regarding propagating specifics from the Nexus API, the following questions were noted:

* Should constraints given by the Nexus API be checked / explicitely stated in the nexus-python-sdk, e.g. should the parameter `org_label` in `nexussdk.organizations.create` be checked to not contain upper case letters or spaces?
* Should terms like `vocab` and `base` be further described in the docstrings of the nexus-python-sdk?

まず nexussdk.organizations.create のエントリポイントと nexus-python-sdk の docstring を確認し、その後、質問を Nexus V1 API の制約と照合します。完了とは、org_label の制限を検証するか文書化するか、および vocab と base を定義するかについて、プロジェクトが判断を記録している状態を意味します。

索引モデルが issue の本文から書いたものです。