Add GW version of the /owners/{address}/safes/ endpoint

[jpalvarezl]

Context

The /owners/{address}/safes/ endpoint is directly queried by the web app is an endpoint known to be problematic due to the heavy load it puts on the database.

Feature

Create a cached endpoint with backend/service models decoupled from each other under

GET /v1/chains/<chain_id>/owners/<address>/safes

Open questions

What webhook payload invalidates this endpoint in case of changes?

We don't have one, we cache for 1 minute

[rmeissner]

How is this issue related to #449

[jpalvarezl]

In its conception it was not. This issue is just a reaction to the service outage. This endpoint was reported to be used directly from the core services and it is also very heavy on the resource side of things. We are just trying to mitigate the load by providing this and heavily cache it.

[rmeissner]

If this endpoint causes issues we should remove it on the core production services (or rate limit it or prevent external traffic) as it is not used by any of our production interfaces

[jpalvarezl]

I've moved this back to review spec so we can maybe include the fields requested by Ivan and address the open questions.

[katspaugh]

If this endpoint causes issues we should remove it on the core production services (or rate limit it or prevent external traffic) as it is not used by any of our production interfaces

This endpoint is now used in the web UI (in the sidebar). So it'd be nice to keep it/cache it.

[rmeissner]

Only for staging or also in production?

[katspaugh]

In prod as well. Since v3.10.0.

Is it killing the service? Should we roll it back?

[katspaugh]

Frontend ticket: safe-global/safe-gateway-typescript-sdk#12