split module into connection and content access by segment

Problem/Motivation

This module and https://www.drupal.org/project/unomi_connect → both provide an admin UI for setting up the connection to Unomi.

I'd like to remove that duplication, and this module's system is superior IMO as it's a pluggable architecture.

However, I don't think that making unomi_connect depend on this module is the right thing to do, as this module adds the access control based on Unomi segments and add base fields to various entity types.

I'd suggest either:

a. Make this project just the connection configuration; move access to new project
b. Make this project just the access; move the connection to a new project
c. Keep functionality in this project, but move access to a submodule.

Related issue on the other project: ✨ Remove connection settings and use either Unomi module's connnection or a new common module Active .

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes