Feature Request/Idea: migrate published datasets from Permalink/FAKE PID provider to another provider

Overview of the Feature Request

We'd like the option to migrate datasets from Permalinks/FAKE DOIs to other PID providers without recreating them.

Perhaps this should also automatically/optionally occur when a dataset is moved from a dataverse that is configured to use Permalinks/FAKE DOIs to a dataverse that is configured to use another type of PID.

Implementation suggestion by @poikilotherm:

It will require extending the DOI provider interface with sth like "allowMigration" so no one moves real stuff to other real stuff and trips over. Migrating datasets from FAKE to a real provider after some initial demo phase etc sounds very reasonable to me, so I don't see why it shouldn't happen.

see discussion on Zulip

We are generally interested in working on a PR for this, but it might take a while until we can get to it.

What inspired the request?

This would be helpful if

• you have created datasets with FAKE DOIs and would like to migrate them to any other kind of non-fake PID
• you have created datasets with Permalinks and would like to migrate them to some externally registered PID, e.g. Handles or DOIs

Any open or closed issues related to this feature request?

not aware

Start by reviewing the DOI provider interface and the linked Zulip discussion about changing a dataverse PID provider via API. Define how published datasets move from Permalinks/FAKE DOIs to another provider without recreation, including safeguards against unsupported real-to-real migrations and behavior when datasets move between dataverses.