Move pin colour detection to browser

[wellemut]

Problem

A clear and concise description of the bug.

for the rate limit issue I can move the tag-color matching to the client's browser instead of server.
Pros: less rate limit, if we change the balloon's color while users are browsing, they won't see the changes in realtime unless they refresh the page.
Cons: will consume user's memory and if the list of color tags grow they may face halted situations.

my recommendation: move the tag-color matching to the browser instead of server because when the csv is small it works on the fly. but we keep the api as well in case we needed to rollback to the server edition.

what do you suggest?