• change package name from polaris to apache-polaris
• reorganize python package catalogs
• union all submodules (cli, polaris) under apache_polaris module
• put polaris generated context into apache_polaris/sdk
• make apache_polaris as a main module

Fixes: #2699

What changes were proposed in this pull request?

Package name

As discussed in the mailing list thread, the majority agreed that a more suitable and compliant name would be apache-polaris according to the Apache Distribution guide

pip install apache-polaris
polaris --help

Catalogs structure

It would be beneficial to modify the directory structure. The current setup can lead to conflicts after package installation because it doesn't create a parent directory to group all apache-polaris related modules together. Instead, it directly places the cli and polaris directories into the root .../site-packages of the active environment.

/site_packages/
├── cli
├── polaris
│  ├── catalog
└── └── management

In the structure I am proposing, all modules related to the project will be placed in the apache_polaris module and will be available for use in code through import apache_polaris.sdk.catalog, apache_polaris.sdk.management and import apache_polaris.cli respectively.

/site-packages/
├── apache_polaris
│  ├── cli
│  └── sdk
│  ├── catalog
│ └── management

>>> from apache_polaris.sdk import catalog
>>> from apache_polaris.sdk import management

Why are the changes needed?

Initial Issue: #2419
Follow up Issue: #2699

Does this PR introduce any user-facing change?

How was this patch tested?

make client-cleanup
make client-regenerate
make client-lint
make client-integration-test
make client-unit-test

CHANGELOG.md