Optimize response time for main endpoints on locksmith

[searchableguy]

Describe the bug Currently, endpoints for metadata take a significant amount of time to respond (7-9 seconds in production) which is not ideal and end us up having to handle it on the frontend with more caution.

We can reduce the response time by eliminating unnecessary and duplicate function calls which take long time to fetch data from the chain.

We should also de-normalize the responses whenever they are beneficial to reduce the overhead of multiple calls or dependent query on the frontend. As an example, when someone requests membership or key metadata, we should also provide lock metadata as a property on that.