Better Author Resolution

### Proposal

This issue is meant to track and manage our various issues related to improving author resolution.

# Examples of Past Improvements
* #9003

We need to compile:
* [ ] Documentation about how our existing author resolution process works
* [ ] A list of existing issues relate to this topic, see: https://github.com/internetarchive/openlibrary/labels/Module%3A%20Identifier%20Resolution
* [ ] A list of common examples of where author resolution is failing
* [ ] A list of agreed upon improvements we could make (and opinions from stakeholders)
* [ ] Basic tests to know whether regressions are prevented
* [ ] Basic metrics / instrumentation to know how often conflations are occurring per month or per some other volume metric.

### Justification

Authors report that conflations are extremely hard to undo and cause a lot of work for librarians and harm the catalog.

The quantifiable impact, how often this problem occurs needs to be examined so we can know how we're doing.

### Breakdown

#### Requirements Checklist

* [ ]

#### Related files

* Resolution: https://github.com/scottbarnes/openlibrary/blob/master/openlibrary/catalog/add_book/load_book.py#L57
* Tests: https://github.com/scottbarnes/openlibrary/blob/master/openlibrary/mocks/tests/test_mock_infobase.py

#### 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.