nats streams max age should be configured

[butonic]

Disk usage of nats streams on disk (or in memory) might grow large. We can forget old kv entries and messages in nats by configuring the streams manually.

1. persistent stores

nats stream edit main-queue --max-age=7d
nats stream edit KV_postprocessing --max-age=7d
nats stream edit KV_userlog --max-age=14d
nats stream edit KV_eventhistory --max-age=14d

2. cache stores

nats stream edit KV_cache-userinfo --max-age=10s
nats stream edit KV_service-registry --max-age=30s
nats stream edit KV_storage-users --max-age=24h
nats stream edit KV_storage-system --max-age=24h
nats stream edit KV_cache-roles --max-age=24h
nats stream edit KV_proxy --max-age=24h
nats stream edit KV_opencloud-pkg --max-age=24h
nats stream edit KV_settings-cache --max-age=10m

Acceptance Criteria:

• TTL Settings are applied at start up
• doublecheck default values

Maybe someone can do this with compose once the opencloud container is running. It contains nats. Or we configure the streams properly when using the nats-go package directly, after #2512

[butonic]

cc @dragonchaser in case you want to know how we configure the max age for k8s deployments.

[butonic]

cc @kulmann you should be able to reclaim a lot of space.

@Svanvith @LisaHue something for the docs?

[aduffeck]

KV_ids-storage-users shouldn't be limited when the posix driver is being used as it would make the according files inaccessible until the next warmup.

I would also suggest to keep KV_activitylog unlimited to not lose activities.

[rhafer]

@db-ot I think we should address this before the next stable release. Needs refinement.