Was: Implement changes required for the scope discussed in the FBC RFC, including appropriate tests.  

operator bundle authors (and automated systems fulfilling this persona) must be capable of expressing and validating operator upgrade graphs containing re-release version representations, including

• re-release naming constraints to ensure superseding relationship is transparent
• adoption and conversion of existing content using the existing freshmaker `olm.substitutesFor` annotation-based API and version expression paradigms

A/C:

• release property validation
• release version bundle name enforcement
• (stretch) a new bundle version type which includes 'base' version and release version considerations which can be used by external callers to reason about bundle sequence ordering
• (stretch) visualization of substitution links in graph renderings