Add options to control federating book data

[Flameborn]

I often find that users of other instances edit existing book data to match what they've read, e.g. change a paperback book to an audio book, rather than creating a new edition. It can also happen that Bookwyrm does not detect that a book is an existing edition, and an author's page has multiple versions of the same book, rather than one version with multiple editions.

As a result, my yearly book reads lists books with missing page numbers, unfilled series name or ISBN, etc, even though I have added this data when creating the book.

To avoid situations like these, it would be great if instance admins had control over whether they accept book data federation from other instances. I see having a enable/disable and perhaps approve only options to do this.

[fofwisdom]

In the case of GoodReads, they don't allow users to edit book information until they have read 50+ books.

This is likely due to the fact that BookWyrm currently allows users to edit the information of already created books by setting their permissions to EDITOR when they sign up.

However, since there are not enough users at the moment, it seems that we need to allow anyone to edit books freely so that more books can be added.

I think Flameborn's suggestion is a good one - it would be nice to design a lock that goes beyond EDITOR's permissions and can be used by moderator level or higher.