[2.0] move domain-specific definitions out of common into their owning modules #1135

currently, the common module contains things that belong to other modules.

• base64 might be removed - it is not used anywhere 0 is this a mistake?
  • Would not remove it, even if unused - since it might be tree-shaken - [WIP] bundler: tree-shaking #1136
• signatures is just an alias which should not exist in the first place
  • see [2.0] common shall be contained #1133
  • see 2.0 dev commons no foreign #1134
• preDefinedLifecyclePhase shall be moved to cyclonedx - the only place where it is used
• commit/diff/patch shall be moved to component - the only place where it is used
  • and also move the identifiableAction with it - it is only used there
  • maybe move to new module heritage? or to component#$defs/heritage/$defs?
• issue shall be moved to release-notes - the only place where it is used
• lifecycle/lifecycles shall be moved to blueprint
  • its description tells that it describes the BOM lifecycle
  • cyclonedx may inherit it from blueprints and override the description
• ordinalVersion shall be moved to blueprint - the only place where it is used
• origin/originRegion shall be moved to component - the only place where it is used