Remove object loading by id and key

[jkoenig134]

Readiness checklist

• I added/updated tests.
• I ensured that the PR title is good enough for the changelog.
• I labeled the PR.

Description

When loading objects was introduced this was the main way to do it. As we now introduce personalized and password protected objects loading by id and key becomes very unsafe.

This will result in runtime@v6.

[codecov]

Codecov Report

Attention: Patch coverage is 96.29630% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
packages/app-runtime/src/AppStringProcessor.ts	0.00%	1 Missing ⚠️

Files with missing lines	Coverage Δ
...ackages/runtime/src/dataViews/transport/FileDVO.ts	100.00% <ø> (ø)
...ibility/facades/anonymous/AnonymousTokensFacade.ts	100.00% <100.00%> (ø)
packages/runtime/src/types/transport/FileDTO.ts	100.00% <ø> (ø)
...ime/src/types/transport/RelationshipTemplateDTO.ts	100.00% <ø> (ø)
packages/runtime/src/types/transport/TokenDTO.ts	100.00% <ø> (ø)
...seCases/anonymous/tokens/LoadPeerTokenAnonymous.ts	100.00% <100.00%> (ø)
...ges/runtime/src/useCases/anonymous/tokens/index.ts	100.00% <100.00%> (ø)
packages/runtime/src/useCases/common/Schemas.ts	100.00% <100.00%> (ø)
...runtime/src/useCases/transport/files/FileMapper.ts	90.69% <ø> (-0.22%)	⬇️
...time/src/useCases/transport/files/GetOrLoadFile.ts	92.20% <100.00%> (-2.04%)	⬇️
... and 5 more

... and 2 files with indirect coverage changes

[Magnus-Kuhn]

The controllers TokenController etc. could also drop some loading methods or change them to private, but I don't think it's necessary and it would mean having to change tests

[jkoenig134]

The controllers TokenController etc. could also drop some loading methods or change them to private, but I don't think it's necessary and it would mean having to change tests

yes, out of scope.

[Milena-Czierlinski]

This will result in runtime@v6.

So what is the strategy for v6? Do we again collect breaking changes on a separate branch? Also, doesn't this PR then require the label breaking change?

[jkoenig134]

So what is the strategy for v6?

No strategy. Just release. We expect minimal to no impact by this change so no long-running communication needed.