fix(logs): update API endpoints to follow REST standard

Now that the batch insert and other operations work, I organised the endpoints to follow REST standard, also removed some unnecessary handlers for logs.

fix(projects): update API endpoints to follow REST standard

Having messy API in initial versions is okay as I'll probably rewrite the whole thing from scratch anyways, but I fixed it for now.

This would've been easier I hadn't decided to stick with standard library for http server, Might switch to echo in coming versions if using vanilla net/http becomes too much of a hassle

feat(chart): use tremor chart for showing log frequency

Tried using D3 and while I might have been able to make charts exactly the way it would have taken too much time, so chose to go with a simple looking charts library

chore: move config to yaml file, add favicon and titles to client pages

env file ended up not having any enviroment variables and only config stuff so moved to a YAML file for config and deleted .env

also created a temporary favicon and added titles to pages

will move rate limiting requests/sec count to config file as well in coming updates

feat(client): create client and basic UI for managing projects

Created a web dashboard for watchman using Next.js, I could have used go html templates but using Next.js I can finish building frontend faster

Might build a client using server side go templates if this works well enough

Also created pages for managing projects

fix(projects): fix minor changes in projects APIs

Needs further updating but changed API enough to get frontend working

feat: projects and logs handlers but no embedded replicas

added all planned handlers for projects and logs and few extra ones as well

could not figure out how to solve SIGSEGV error with turso's embedded replicas

could use a minio server and systemd timers for db backups

infra(batman): create basic structure and middleware

created a basic file structure, its not ideal but good enough for now

also copied code for rate limiting middleware, might have to change it if I decide to use a reverse proxy

and a simple request ID middleware