Consistent proposal naming scheme

This proposal suggest to introduce a consistent naming scheme for all proposal types.

Problems with the current naming scheme
The current naming scheme works pretty well for most departments. While some departments mask their proposals by giving them less intimidating names (e.g. writing content or game mechanic), the programming department uses the term code proposal for their implementation-focused proposals.

As we use a consistent naming scheme for all proposals - masked and obvious ones - the programming department follows this scheme as well. Therefore fleshed out code proposals that are ready to be reviewed in detail by other developers are currently called proposed code proposals.

Type I proposals

 * Work in progress proposal
 * Proposed proposal (e.g. Proposed code proposal)
 * Accepted proposal
 * Implemented proposal
 * Deprecated proposal

Type II proposals

 * Work in progress proposal
 * Proposed proposal (e.g. Proposed code proposal)
 * Established proposal
 * Deprecated proposal

Type I proposals

 * Work in progress proposal
 * Drafted proposal (e.g. Drafted code proposal)
 * Accepted proposal
 * Implemented proposal
 * Deprecated proposal

Type II proposals

 * Work in progress proposal
 * Drafted proposal (e.g. Drafted code proposal)
 * Established proposal
 * Deprecated proposal

Possible implementation
We shouldn't bother with such a task due the huge amount of work it would take to implemented the suggested changes. However we actually use wiki extension (ReplaceText) that can mass rename articles and their content. Therefore implementing the suggested changes would be rather easy and wouldn't cause any extra work.