feat: HTTP REST API: Store Client API

[jm-clius]

Background

This forms a subtask of #1076.
Nwaku nodes operating as 13/WAKU2-STORE clients can use the store protocol to query waku archive nodes for historical, cached messages.
Currently these queries can be triggered in clients in one of two ways:

• an internal Nim API call for store clients
• an external call to the exposed JSON-RPC API

The only way to externally trigger store queries to a remote archive is therefore using the JSON-RPC API.

However, the JSON-RPC API is clunky to use and call signatures outdated. As such, we've started migrating to an HTTP REST API. What's more, we've since simplified and flattened the internal Nim API for store client queries, removing unnecessary constructs like nested content filters, which still exists on the JSON-RPC API.

Suggested solution

Create and expose a Store Client HTTP REST API functionality. It should use the existing Relay REST API as inspiration and follow the same patterns and structure. Although, the JSON-RPC API can be referred to, the new API method should follow the simplified internal API to construct the query objects.

As part of this effort, #1575 should also be addressed - which simply allows store client API endpoints to be installed and exposed, regardless of node configuration.

Acceptance criteria

• working HTTP Store Client REST API to perform history queries on remote archive nodes
• sufficient unit tests for basic functionality
• integration of Store Client API into the wakunode2 app

[Ivansete-status]

As per @jm-clius advise, we will use this HistoryResponse object instead of the one described in get_waku_v2_store_v1_messages and currently used by the JSON-RPC API.

That will make the solution simpler.