Auto clear revisions in a specified timeframe

[DanielHudson2]

Post revisions can quickly grow and start to cause some issues.

Specific example, a site which had ACF repeater fields with a lot of data in them on its homepage had over 600 revisions, the site was getting out of memory errors when loading the edit page for it because it was loading all the meta for the revisions.

Unsure if this is really an issue with block editor sites but it is a potential one for "classic" sites which utilise ACF for their content.

Also makes sense to have a function to clean old data up

[brettsmason]

As discussed, we should look at limiting the number of stored revisions to something like 25 (maybe with a filter to adjust this limit).

[DanielHudson2]

@brettsmason we have a way to do that already in Nebula https://github.com/eighteen73/nebula/blob/main/config/application.php#L126 we could just set the default there to be 25 instead of true and then it can be overridden per project via the .env

Should we stick with that or look at removing it from there and defining it in Orbit? as its a constant I can't redefine it once Nebula sets it