fix(web): Speed up lookups on large datasets

[ghost]

Description

Fixes: #4180

How Has This Been Tested?

time parsing library caching + o(1) instead of .find

• Test A
• Test B

Checklist:

• I have carefully read CONTRIBUTING.md
• 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/)

initial pr for
#4180

[immich-push-o-matic]

Label error. Requires exactly 1 of: changelog:.*. Found: 🖥️web. A maintainer will add the required label.

[alextran1502]

Can you show some benchmarking on small/medium/large libraries? Otherwise we won't be able to justify the changes to have it merged

[ghost]

Can you show some benchmarking on small/medium/large libraries? Otherwise we won't be able to justify the changes to have it merged

upd: was thinking of time related caching while typing this:

i have done it, on large datasets 1-20ms vs 1000+ ms.
small ones will be similar, medium will be following the large datasets scenario, should be kinda obvious considering the callbacks speed in js engines

its basically the same little unnoticeable bottleneck you were describing in your PR related to casting and casting taking 1 second

[ghost]

string allocation slows down entire thing

[ghost]

can be fixed with any fast hashing algorithm but since i cant find any usage of any kind of hashing function in codebase yet id rather close, but keep in mind its a second still