Separate Requirements and Evaluation templates

Major changes to code:

• Allow deploying to Heroku from the master branch (a GitHub action has been set up for this)
• New and updated views to support the new evaluation template, and "not fillable" requirements template.
• Other templates have been removed from GUI but are still present in code base.

Major changes to generated documents:

• The document is now split into two versions:
  • Requirements: Like the previous version, but with the fillable columns removed.
  • Evaluation: A new, slimmer version which is more suitable for evaluation in a procurement activity. It yields a conformance score %, using the method described in our sample RFx language.
• AAACT document guides are linked from the last Annex of the Requirements documents (guidance for creating accessible documents)
• “Scope” is included in all documents, even though these include all clauses.
  • Rationale: If a user of the documents removes a section, they can also remove those clause numbers from Scope for clarity.
• Filenames are more descriptive

Note that the evaluation templates do not include separate weights for each requirement. The functionality for this has been roughed-in to the code. As this feature requires further discussion it has not been fully implemented or exposed in the GUI.