feat: improved api endpoint for listing resources

[dacbd]

An "optimized" api endpoint for retrieving resources. In the system, currently it seems there is a get all resources endpoint (could be quite expensive as the number of resources grow) and a cel query version, which can be expensive for cel reasons.

I think the bare requirement for an efficient v2 List Resources endpoint is the ability to filter on version and kind.

Bonus points for accepting any top-level resource key. extra points if metadata and config are jsonb columns and we can support a jsonpath query for those fields.

Overall the intent is to allow the cli tool ctrlc to have a ctrlc get resources command that can behave like kubectl get <resource> -l key=value

[mleonidas]

This pr added the search endpoint, we'll need to update the cli repo to utilize it