Add protected fields + suggested edit via merge queue

### Problem

### A clear and concise description of what you want to happen
In the context of web books, we want individuals to be suggest new web books via a merge queue (#9624).

As part of this process, one might edit a book, add the information to make a web book (e.g. URLs, type, such as PDF, etc.) and also make other edits. We want the 'normal' edits to go through and the 'web book edit' to go to a web book merge queue.

But if we do this, perhaps we could expand this logic to cover other fields we might want to 'protect' in some way, but also allow people so suggest edits via a queue.

This issue needs further fleshing out from insight gained while working on #9624.

### Expected behaviour / screenshots (ex: Figma design screenshots for UI feature)

### Additional Context

Note: this issue is *NOT* yet ready to be worked on, and needs a breakdown, likely after #9624 is complete.

### Proposal & Constraints

### What is the proposed solution / implementation?

### Is there a precedent of this approach succeeding elsewhere?

### Which suggestions or requirements should be considered for how feature needs to appear or be implemented?

### Leads

### Related files

### Stakeholders

### Instructions for Contributors

- Please [run these commands](https://github.com/internetarchive/openlibrary/wiki/Git-Cheat-Sheet#working-on-your-branch) to ensure your repository is up to date **before** [creating a new branch](https://github.com/internetarchive/openlibrary/wiki/Git-Cheat-Sheet#making-changes-and-creating-a-pull-request) to work on this issue and **each time after** pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.