fix(web): fix thumbnail hover link overflowing past thumbnail bounds

[Snowknight26]

Description

This fixes the height and z-index of the <a> element when hovering over asset thumbnails. Because the a element is absolutely positioned and shifted down 41px, it was possible navigate to the asset by clicking below the thumbnail when you didn't intend to navigate to it. Now that the z-index is correct, the element no longer has to be offset, fixing the link position.

This also fixes the search page showing scrollbars when hovering over thumbnails from the last row of results on the search results page.

How Has This Been Tested?

• Hovered over and clicked on assets in the asset viewer
• Hovered over and clicked on assets on the search page
• Hovered over and clicked on additional assets when in selection mode

Screenshots (if appropriate)

Before:

After:

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation if applicable
• I have no unrelated changes in the PR.
• I have confirmed that any new dependencies are strictly necessary.
• I have written tests for new code (if applicable)
• I have followed naming conventions/patterns in the surrounding code
• All code in src/services/ uses repositories implementations for database calls, filesystem operations, etc.
• All code in src/repositories/ is pretty basic/simple and does not have any immich specific logic (that belongs in src/services/)

[NicholasFlamy]

What happens if you do this?

Suggested change

	class="absolute z-30 {className} top-[41px]"
	class="absolute z-20 {className} top-0"

[Snowknight26]

From what I tested previously, this offset is needed, otherwise you can't click on the checkmark to actually start the selection process.

[NicholasFlamy]

Oh, I figured out a solution.
Change z-30 to z-20 and on the div below change z-20 to z-30 and you can then set 0 like in my suggestion.

[NicholasFlamy]

So, this issue was a regression, as it doesn't occur on v1.122.2

Correction, this issue does occur on v1.122.2. I didn't realize it behaves differently if there is an asset directly below it in the same date group.