feat: support for user linked project permissions

[tomwwinter]

related: https://github.com/Aam-Digital/internal/issues/21

[sleidig]

Looks good so far, but isn't this currently still missing the core of the logic, i.e. that the project field is used to filter out docs during replication?
Or can "projects" now somehow be used in configured rules?

[sleidig]

small code block, but also for future proofing I would suggest we put the UserInfo creation in a service rather than duplicate it.

[sleidig]

Looks good so far, but isn't this currently still missing the core of the logic, i.e. that the project field is used to filter out docs during replication? Or can "projects" now somehow be used in configured rules?

Okay, understood now that this simply works out of the box 😄
(placeholder is available as ${user.projects} for the permission config)

• Let's add the details about this placeholder to the Dev Docs: https://aam-digital.github.io/ndb-core/documentation/additional-documentation/concepts/user-roles-and-permissions.html
• Let's remove the documentation about permissions config from the README here, replacing with a link to the docs

[sleidig]

Looks good!

Could still remove that code duplication here #147 (comment)
but we can also do this once we touch that code again.