Reject creating baselines for requirements that are still on drafts
Sometimes, requirements can be:
On an unsaved draft,
On a non-Confluence page,
It is possible to create baselines. Rather than silently fail and not include the requirement to the baseline, or including it without a link to the original page, we'll reject the creation of the baseline and ask the user to fix their query.
As a side note, we'll obviously also fix the NullPointerException that arises from displaying a baseline with requirements that don't have a version.