Component and profile versioning/deprecation

[twagoo]

This ticket covers the back end aspect of component and profile versioning/deprecation, originally Trac #142. Corresponding front end issue: #66 and #67.

Concrete tasks:

• Index status information in the database
• Add parameter to rest service (/components, /profiles) to toggle inclusion of deprecated (default: hide)
• Implement way of altering status (probably best via normal PUT update, parse status in header)

Description of original Trac ticket:

Note: Trac #571 covers support for public drafts (publicly visible private components), a subset of the functionality described here, without the lifecycle status properties specified in CMDI 1.2

This enhancement should enable an owner of a component to designate a new component or profile as the new version of an existing a component, marking the existing version deprecated.
There will (at least initially) be no mechanism to deal with backwards compatibility, i.e. published components will remain unchanged but users will be strongly encouraged to use to the new version. The status will be represented in the XML/XSD of the profile (see #146).

This is the first and most important step after the required general component schema update in implementing the Component Lifecycle Management features of CMDI 1.2.

Also take note of the envisioned set of '''views''' that strongly relate to this (and the additional option to mark development components for review). See ComponentVersioning#Viewsworkspacesandregistries.

[twagoo]

Status indexing was implemented in 5a07e78

[twagoo]

Status information is taken from component spec header and stored in the database (part of changes in 73b488d that also fix #2)

[twagoo]

As of 8c1bf08, status for profiles and components can be assigned/retrieved via {id}/status (GET/POST). TODO: same for successor.

[twagoo]

As of b9cfd73, successors for profiles and components can be assigned/retrieved via {id}/successor (GET/POST).

[twagoo]

Component/profile listing can be filtered with the status query parameter. Default behaviour depends on user space. Implemented including tests as of 40ae662