Do not require setup of PID credentials for development environments

[djbrooke]

Developers wanting to hack on Dataverse or evaluate Dataverse currently need to set up a test account for PID minting. This makes it harder to hack on Dataverse, so consider removing this dependency from the process.

Production installations and those wanting to test the full publish flow would still need some way to mint PIDs.

Other ideas welcome, but the goal is reducing what's needed to work on and/or run the code in a development/test environment.

[matthew-a-dunlap]

I just spun up a related issue on not requiring an email server for development #5328

[poikilotherm]

This might be related to #4106, #5082 and others. @4tikhonov and I discussed plans about implementing an external service for PID minting that is used via some REST API or similar. That would offload maintenance of PID providers from the main project and it might offer a solution to have a dummy/local only PID minter for demo/dev/... purposes available.

Maybe we can ask @4tikhonov during the next Community Call how far they got at DataverseEU with this? (I had no time to look into this yet, because of priority goal #5292 etc.)

[djbrooke]

We'll use internal mock implementation of a PID provider. It should be obvious that it's a test PID through the UI.

[matthew-a-dunlap]

For what its worth, this is the current error on my dev machine. Forgive my randomly spammed dataset name: