feat(persistence): add file_storage

[OverOrion]

Note

This needs a bit more investigation as it is possible to lose logs even with using storage.
For this reason the PR will be a draft first.

Found logs: 93
Checking for subscription-sample-1 in deployments/receiver-collector logs, expected: 100
Found logs: 93
Checking for subscription-sample-1 in deployments/receiver-collector logs, expected: 100
Found logs: 93
Checking for subscription-sample-1 in deployments/receiver-collector logs, expected: 100
Found logs: 93
Checking for subscription-sample-1 in deployments/receiver-collector logs, expected: 100
Found logs: 93
Checking for subscription-sample-1 in deployments/receiver-collector logs, expected: 100
E2E test failed
make: *** [Makefile:209: e2e-test] Error 1

 kubectl logs --namespace example-tenant-ns log-generator-1706798709-5675dcd8fc-9hkqr  | grep  "HTTP/1.1" | wc -l
100

[OverOrion]

Yeah, the CI fails with the same behaviour:

https://github.com/kube-logging/telemetry-controller/actions/runs/7743484104/job/21115138844?pr=20

[OverOrion]

A recently merged PR into contrib (30914) might explain what I think is happening here:

## Offset tracking

`storage` setting allows to define the proper storage extension to be used for storing file offsets. 
While the storage parameter can ensure that log files are consumed accurately, it is possible that
logs are dropped while moving downstream through other components in the collector.
For additional resiliency, see [Fault tolerant log collection example](../../examples/fault-tolerant-logs-collection/README.md)