Allow Super Librarians to quickly move an edition to a new work

### Feature Request

### Problem / Opportunity

My biggest pet peeve as a librarian is how tedious it is to move editions to a new work. It's all too common for different works to be grouped up into one, and needing to move them out of the work one-by-one.

To move an edition to its own work, you currently need to...

1. Open the edition's page
2. Click Edit
3. Scroll down to "What work is this edition of"
4. Replace the work ID with "--" and wait a few seconds for "-- Move to a new work" to show up
5. Scroll down, add an edit note, click save

This doesn't sound that bad on paper, but when you need to do it 50 times in a row it becomes clear how much time is wasted.

**Note:** This isn't about moving an edition to another work, this is about creating a new work and moving an edition to it. I'm aware you can drag and drop editions to other works, but AFAIK there's no equivalent to move it to a new work.

### Proposal

Here's a mockup I have where you can move an edition to a new work just by clicking a button when one (or more) editions are selected. This should make it super easy to decouple works, without having to manually go into each one and spend 4x the time.

### Breakdown

### Related files

Refer to [this map of common Endpoints](https://github.com/internetarchive/openlibrary/wiki/Endpoints):
*

### Requirements Checklist
Checklist of requirements that need to be satisfied in order for this issue to be closed:
* [ ]

### Stakeholders

*

### Instructions for Contributors

* **Before** [creating a new branch](https://github.com/internetarchive/openlibrary/wiki/Git-Cheat-Sheet#making-changes-and-creating-a-pull-request) or pushing up changes to a PR, please first [run these commands](https://github.com/internetarchive/openlibrary/wiki/Git-Cheat-Sheet#working-on-your-branch) to ensure your repository is up to date, as the pre-commit bot may add commits to your PRs upstream.

Start with the linked map of common Endpoints and the edition-page Edit flow described in the issue; no source files or tests are identified. Use the mockup and existing selection behavior to clarify the interaction. Done should let a librarian select one or more editions, create a new work for each intended move, and verify the editions are moved correctly.

Written by the indexing model from the issue text.