fix(mimirtool): Make remote-read actually return data

[julienduchesne]

Since #9156 probably, all the remote read commands return no data

I added a missing error return using timeseries.Err() and got this error: mimirtool: error: chunkedReader: message size exceeded the limit 0 bytes; got: 361 bytes, try --help which lead me to find that we need to pass in ChunkedReadLimit on the client

I set it at a default 1 MiB and configurable through a flag

Checklist

• Tests updated.
• Documentation added.
• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
• about-versioning.md updated with experimental features.

[dimitarvdimitrov]

1MiB is also what mimir uses by default

mimir/pkg/querier/remote_read.go

Lines 37 to 40 in 7485d55

	// Maximum number of bytes in frame when using streaming remote read.
	// Google's recommendation is to keep protobuf message not larger than 1MB.
	// https://developers.google.com/protocol-buffers/docs/techniques#large-data
	maxRemoteReadFrameBytes = 1024 * 1024

SGTM, but maybe having something like 10-100MiB won't hurt so mimirtool is interoperable with other implementations that might choose slightly higher values.

[dimitarvdimitrov]

I think the limit before the PR you linked was 50MiB, so we can restore that

// DefaultChunkedReadLimit is the default value for the maximum size of the protobuf frame client allows.
// 50MB is the default. This is equivalent to ~100k full XOR chunks and average labelset.
const DefaultChunkedReadLimit = 5e+7