[Kitsu API] Deals with the case where there is no small/tiny image

[Kcchouette]

In the case of a recent anime, here the content we have back for poster:

      "posterImage": {
        "original": "https://kitsu-production-media.s3.us-west-002.backblazeb2.com/anime/44979/poster_image/9f6b8e791778abde38ca7e711327f50e.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=002d6013655cdc00000000003%2F20220116%2Fus-west-002%2Fs3%2Faws4_request&X-Amz-Date=20220116T214041Z&X-Amz-Expires=900&X-Amz-SignedHeaders=host&X-Amz-Signature=602c57bd3964a1aa4074cefb1f0e39d30a1ff6b46d23cd703cc12097b70959df",
        "meta": {
          "dimensions": {}
        }
      }

(for CUE anime / id = 44979)

So we have no small/tiny poster and so trackma keeps crashing

[ahmubashshir]

@Kcchouette, try writing more descriptive commit message than just "Update X" or "Fix Y"
Read these: 1 2 3

[Kcchouette]

@ahmubashshir you are right, but when merging you can squash it
Here title is understandable

[ahmubashshir]

People do more merge than squash, and the "Update X/Y" commit messages don't sense in that situation.

Fun fact: you didn't have to write a good description and title for the PR at all, if you write commit messages properly, github-cli uses the first commit title as PR title and generates the body from either first commit message body or from the title of all commit unmerged in that branch.

[FichteFoll]

Should we have a fallback to 'original' if 'small' cannot be found?

[z411]

image is used by the details dialog. How small is the small thumb? And yes I think a fallback to original would be sensible as the details dialog can be as big as you want to.