Detect if ISBN field contains ASIN for Metadata search

[DarthNerdus]

ASIN search PR

This PR allows a user to paste in the ASIN of a book into the ISBN field.

I initially made changes to add an ASIN field, but that felt like a much larger change for the same effect and added unnecessary UI bloat. An argument could be made for updating the label to indicate that ASIN is supported, but for now I implemented this as an "easter egg". If you type in an ASIN, instead of failing because fetch-ebook-metadata was explicitly told it was an ISBN, it will now check if it is an ASIN and proceed with the same metadata lookup.

Other items in my fork

I do want to briefly tell you what my plan is for many of my little edits. For small, atomic changes I'll be opening PRs. But I have other things I've changed to my preference (default pagination size) or added functionality that I'm unsure whether it fits the goal of the project. For those, I am maintaining a fork/branch that I am constantly rebasing against your main branch whenever you push changes. In this way, I'm maintaining a set of atomic patches you are free to pull in (or I will PR) and others can use. A few examples right now, if you'd like me to push them up too:

• Jumping from search to looking up a book to add (autopopulating the query), intended for "check if I have this, add if I don't" workflow.
• Homepage lists the latest things read/dropped based on when they were read, not when the reading event was created.
• Automatically selecting the latest year on history and stats pages

[bayang]

Ok, that looks nice, thanks for your work on Jelu. For backend related code I would like some tests please, frontend obviously should be tested as well but I don't have enough time, so I try to at least maintain a well tested backend codebase.

For your other features :

• Automatically selecting the latest year on history and stats pages seems ok, you can submit a PR
• Homepage lists the latest things read/dropped based on when they were read, not when the reading event was created. -> you can submit a PR, I'll check how it looks
• Jumping from search to looking up a book to add (autopopulating the query), intended for "check if I have this, add if I don't" workflow. -> I don't get this one, can you elaborate a bit please ?
• concerning pagination size, maybe we could make it configurable, I don't know. I chose 24 initially because it fitted rows of 8 books I think. Also I don't know the performance hit on the DB with a bigger page size.

[DarthNerdus]

Updated to add tests asserting the three different test paths match correctly.

[DarthNerdus]

@bayang -- Here's a loom video of the feature to jump from search to add.

I can submit a PR without the focusing that you see happening. I like the focusing because it allows me to progress between the views via keyboard, not mouse. I doubt that'd be preferable for everyone though.

No sweat if this isn't wanted, was definitely more of a "me" thing I can maintain.

EDIT: ...it helps to link the video... 🤦🏻

https://www.loom.com/share/3e8f79981445434e83f9e9cdab4e9b00?sid=a5fc033e-c7e3-433b-ac2f-162e28f0ead0

[bayang]

:tada: This PR is included in version 0.55.0 :tada:

The release is available on:

• v0.55.0
• GitHub release

Your semantic-release bot :package::rocket:

[bayang]

@DarthNerdus the feat in your video looks nice, you can submit a PR as well if you want.