When updating a very large Journal Article with many versions, update times is really long.
A solution is now to introduce a configuration which allows for a cap to be placed on how many versions an article can have.
When a webcontent article version is over the config cap
Then any article version over this cap will be expired, starting with the lowest version number.
When a system admin wants to change the cap
Then he can access a config to change the number of versions