refactor: Extract ObjectAccess and Administrative permissions into Permission model in admin slice

[seakayone]

• Extract ObjectAccess permission to admin slice
• Replace EntityPermission with ObjectAccess permission
• Extract Administrative permission to admin slice
• Introduce common Permission trait
• Inline PermissionsMessagesUtilADM.scala

Pull Request Checklist

Task Description/Number

Issue Number: DEV-

PR Type

• build/chore: maintenance tasks (no production code change)
• docs: documentation changes (no production code change)
• feat: represents new features
• fix: represents bug fixes
• perf: performance improvements
• refactor: represents production code refactoring
• test: adding or refactoring tests (no production code change)

Basic requirements for bug fixes and features

• Tests for the changes have been added
• Docs have been added / updated

Does this PR introduce a breaking change?

• Yes

Does this PR change client-test-data?

• Yes

[codecov]

Codecov Report

Attention: Patch coverage is 95.49550% with 5 lines in your changes are missing coverage. Please review.

Project coverage is 88.74%. Comparing base (62260e4) to head (6454b6d).
Report is 6 commits behind head on main.

Files	Patch %	Lines
...knora/webapi/messages/util/PermissionUtilADM.scala	91.30%	2 Missing ⚠️
...rg/knora/webapi/responders/v2/ResourceUtilV2.scala	66.66%	2 Missing ⚠️
...api/responders/admin/PermissionsResponderADM.scala	95.83%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3152      +/-   ##
==========================================
- Coverage   88.79%   88.74%   -0.05%     
==========================================
  Files         265      266       +1     
  Lines       22260    22274      +14     
==========================================
+ Hits        19765    19767       +2     
- Misses       2495     2507      +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[BalduinLandolt]

looks good, thanks!

[BalduinLandolt]

comment (non-blocking): I find the term token somewhat confusing because it makes me think of JWTs. But I can't think of anything better for now. Maybe in the future we can try to think of something more descriptive.

[seakayone]

I am happy to hear any suggestions.

The token contains now the value which is actually written as a token in the hasPermission property:

• ... knora-api:hasPermissions "CR knora-admin:Creator|M knora-admin:ProjectMember|V knora-admin:KnownUser|RV knora-admin:UnknownUser"
• ... knora-base:hasPermissions "ProjectAdminGroupAllPermission|ProjectResourceCreateRestrictedPermission http://www.knora.org/ontology/0001/example#person,http://www.knora.org/ontology/0001/example#event"

For example the full name for all administrative Permissions like ProjectAdminGroupAllPermission or the abbreviation for the object access permissions like CR. Other property names I have considered were: abbreviation, code, symbol, name, wdyt?

[BalduinLandolt]

I spontaneously like code best. But at the end of the day, I'm ok with either of those as well as with token