Metadata: Files with an altitude out of range are not indexed

[lastzero]

If a media file's metadata has an altitude value that is out of range, such as 4294967284, indexing fails with logs that look like the following:

2023-01-31 18:37:43 ERRO index: failed adding main jpg file 'Misc Photo/2013/2013-08-25_15-54_06.JPG'
2023-01-31 18:37:43 ERRO index: %!s() in 'Misc Photo/2013/2013-08-25_15-54_06.JPG' (find or create photo)
2023-01-31 18:37:43 INFO index: matched 1 label with 2013-08-25_15-54_06.JPG [727.48731ms]

This is probably because Go uses a 64-bit integer, while MariaDB uses a 32-bit integer. We will add a range check (about the diameter of the earth) to prevent this. PhotoPrism defaults to an altitude of 0 in this case.