Approval process changes

Problem

This issue combines changes to the Approval flow.

To provide a departmental standard for project documentation and approval, the currently existing Project and Document types are available to other Divisions.
A slight relaxation of naming and labelling is expected to accommodate for multiple Divisions.

[x] Projects have a Team of DBCA staff, defined in Project TeamMemberships.
[x] Project Team members have the permission to author Documents, such as Concept Plan, Project Plan.
[x] The primary reviewer of Documents is the SDIS Program leader. RFMS “Programs” are the nine RFMS regions, CEM “Programs” are the five CEM branches.
[x] The secondary approver of Documents is the Executive Divisional Director. This means that all and only BCS projects notify the ED BCS for approval, whereas all and only RFMS projects notify the ED RFMS for approval. The EDs have the choice to nominate an assistant, e.g., their A/Dir or their EA, to receive these notifications on their behalf.
[x] All Document and approval workflows and Project lifecycle stages shall be identical across all Divisions, except for annual updates.
[x] Only BCS projects shall require annual updates. This prevents but does not rule out that other annual reports are generated for other Divisions.
[x] Update docs: Add section for authors, reviewers (program leaders, branch managers, regional leaders), approvers (EDs or their A/Dirs or EAs). Common tasks, common pitfalls. Generic language.