Architecture: Separate PID record retrieval from PID creation.

[Pfeil]

For example, in sandboxed mode, it only resolves sandboxed PIDs. This is due to the current architecture: Resolving is part of a PIT-Service-Implementation, so the configured implementation will be used. There are several reasons why this is an issue:

Caused Issues which should be fixed with this approach:

• Type-Checking uses an extra resolving mechanism, so it can always resolve handle PIDs for that.
• Only one kind of PID system can be used for resolving PIDs.
• Only the configured kind of PID can be resolved.
• Sonarlint scored detected that one implementation has too many responsibilities. We should take it as a sign, considering the previous issues. Split read and write operations into different modules #58

---

It might be a good idea to not only make a separate module, but make this meta-resolving a separate library for further re-use.

• I think we have some starter for this in service-base or repo-core
• This repo might be interesting also (although it is unfortunately a rest service), specifically this file: https://github.com/FC4E-WP5/fc4eosc-PIDMR-api/blob/devel/files/providers.conf