No, AFAIK there is no support for handling versioning for you. I think because Liferay only needed it for journal articles and files, there was no need to build an infrastructure to serve two implementations, it was likely just easier to do the version management separately.

Plus, when you look at the Liferay version handling for these entities, it can get quite complicated in the features they allow for, etc., but even between journal articles and files there are differences in what they both implement.

It will end up being up to you to roll your own solution. I would just recommend completing the analysis and design up front and clearly documenting for yourself, your team, your client, etc. what is going to be supported and how and why... You'd be amazed at how many bugs get opened because of ambiguity in what the Liferay versions are for, etc., and without a documented design you won't really be able to push back on things like "works as designed", etc.