feat: add last online timestamp to archive and drivers

[SionoiS]

Description

This PR adds a way to save a timestamp periodically so that we can know when the node was last online.

This feature will be used for a future store resume functionality.

Changes

• sqlite driver set/get last online timestamp
• postgres driver set/get last online timestamp
• postgres migration
• archive set/get last online timestamp
• archive periodically set last online timestamp
• drivers test

[github-actions]

This PR may contain changes to database schema of one of the drivers.

If you are introducing any changes to the schema, make sure the upgrade from the latest release to this change passes without any errors/issues.

Please make sure the label release-notes is added to make sure upgrade instructions properly highlight this change.

[github-actions]

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:2916

Built from 1c470e7

[SionoiS]

Do we really need a migration just to add a new table?

[Ivansete-status]

Thanks for that @SionoiS ! Nevertheless, I'm curious about the underlying deliverable/milestone :)

[SionoiS]

Thanks for that @SionoiS ! Nevertheless, I'm curious about the underlying deliverable/milestone :)

It's part of Store sync waku-org/pm#131 a protocol/heuristic to resume store services after an offline period

[Ivansete-status]

It's part of Store sync waku-org/pm#131 a protocol/heuristic to resume store services after an offline period

Cool thanks! In that case, I think is better to have a separate sqlite database where we store that info. Similar to the peers.db where we store peers data. The reason is that in Status we have two nwaku nodes that share the same PostgreSQL database.