Add prometheus monitoring to frontend

[MichaelDeng03]

What's been implemented:
Prometheus exporter using open telemetry so that prometheus backend in apps/prometheus can scrape the frontend's /metrics endpoint.

Info dump:
Predominantly yoinked from this dudes solution. Relevant parent discussion regarding sticking a prometheus exporter into a next.js server
Next.js version 15 makes telemetry stable, so you don't need to configure nextConfig w/ experimental telemetry hook.
I used a similar solution in eliza
Next.js documentation on adding instrumentation
Why prom-client was not used

Quickstart:

make run-prometheus
make run-frontend # couldn't get get outside of docker to work, will look at this l8r

prometheus will be available at http://localhost:9090
make sure that frontend was discovered in the status -> service discovery drop down

you can run some queries on prometheus about your frontend:
{job="frontend"} will list all metrics (go to table view)
example metric w/ nothing fancy:
nodejs_eventloop_time will graph your eventloop time (go to the graph)

TODO:

• Update prometheus backend app to see frontend
• Update aws (holy friggin frick)
  • Figure out how to expose and restrict port 9464

[MichaelDeng03]

monsieur @abjjabjj if you could take a look at the instrumentation in this pr when you get back, that would be great
it's missing a few things, but available for playing around with locally
Here's a quickstart, I'll update the pr comment with this as well

make run-prometheus
make run-frontend # couldn't get get outside of docker to work, will look at this l8r

prometheus will be available at http://localhost:9090
make sure that frontend was discovered in the status -> service discovery drop down

you can run some queriers about your frontend,
{job="frontend"} will list all metrics (go to table view)
nodejs_eventloop_time will graph your eventloop time (go to the graph)

[MichaelDeng03]

ill put a pr for this into main after 34 is merged
there's a few more snags that I have to work through tho