feat: feeds check

[acha-bill]

No description provided.

[istae]

nice work, some comments

[gacevicljubisa]

The purpose of the feed check is to enable running it as a regression test. To achieve this, we need some output from the first run that can be reused in subsequent runs (e.g., after updating the Docker image of the node).

The process of generating and retrieving this output should be straightforward. The output can be displayed in the console, but we could also store it in a file for convenience.

To simplify automation, we could follow a sequence of commands like this:

beekeeper check --cluster-name=default --checks=feed --output=example.yaml  
beekeeper restart --cluster-name=default --image=ethersphere/bee:latest  
beekeeper check --cluster-name=default --checks=feed --input=example.yaml  

However, additional modifications to Beekeeper would be required to handle these two flags (--input and --output).

This approach can be generalized for other regression tests in the future.

@istae, @acha-bill What are your thoughts on this?

[acha-bill]

This feed check is in 2 parts—the integration and regression tests. We went with an approach similar to long availability tests for the regression test. We try to retrieve a feed that already exists on public testnet

The approach you propose is neat as well since it can be run locally or in CI without the public testnet.
If we agree to proceed with this new approach, I can strip off the regression part from this PR and keep the integration.