feat: prometheus metrics

[Galeaf11]

Problem

As the number of components increase in lpms-server, the complexity of diagnosing bugs increases.

Solution

Implement prometheus metrics for monitoring the components of lpms-server, particularly:

• Express monitoring:

• Monitor all response codes that are sent from express, ie 200, 400, 500, etc etc.

• Waku monitoring:

• How frequently messages arrive via waku - including monitoring on what contentTopic
• Peer connect / disconnect events (ie. when waku connects to a new node, or drops the connection to an existing node.
• Monitor malformed protobuf messages.

• Videre monitoring:

• Each time an 'ask' is received (also store the checkIn / checkOut dates, and other query parameters)
• Each time a 'bid' was made (ie. a space was offered, and what space was offered)

• Booking engine monitoring:

• Time taken to process a query (including if an offer was made) - this is to allow monitoring of the performance for the query engine, breaking down by number of offers made in responding.

• Blockchain monitoring:

• Each time a user makes a booking (including gem and wad)
• Each time a settlement is made.