🚀 Feature Request: Allow non-destructive plugin slug renaming

[jdevalk]

Describe the problem that needs this feature

If we have the plugin slug fair-plugin, and want to change that to fair-connect, that currently leads to the plugin being disabled on update. We should deal with that better.

Describe the solution you'd like

1. A redirect from old-slug to new-slug.
2. The ability to update from old-slug to new-slug without the plugin getting deactivated.

This requires a change in AspireCloud as well as in FAIR Connect, the ticket for FAIR Connect is fairpm/fair-plugin#339

[chuckadams]

I'm thinking a literal redirect is the best way to go about this, just redirect package requests and any request with plugin_information or theme_information request to the canonical source by rewriting the query string. For legacy plugins, this should just work out of the box, as long as there aren't any assumptions that the slug from the API response is the same as in the request.

This would be more or less a manual process and driven by some kind of config file/table and admin UI. The slug namespace is still flat, so some human review process will likely always have to be in there.