Reorganise the 4.2 release notes and changelog to include new sections for documentation and maintenance. This helps to highlight the most relevant changes from the perspective of a developer wanting to know what they can expect from an upgrade, while still recognising less visible contributions. Also update the "committing code" docs to explain the new classification scheme.