Admin interface for project specific configuration, capabilities and templates

## User Story

**As a** _an administrator_,

**I want** _the ability to modify templates for export forms, customize emails and modify user capabilities_

**so that** _I can customize OCWA on a project by project basis_.

# Conditions of Satisfaction
- an admin interface available to users in a specific admin authorization group
- all configuration available to an admin is project specific/group authorization
- authorization/authentication integrates with Keycloak/Active Directory, will support one or more projects
- the interface allows admins to to add, remove, modify fields in the export form
- all changes made in the front end forms are supported by the backend API
- relevant changes made to the front end are reflected/cascade down to the reporting interface, the downloads interface and the 'my requests' interface
- admin interface allows modification of form templates including adding, removing and updating check box fields, text fields, labels, and select lists
- templating admin interface permits re-ordering components on the page
- admin interfaces permits configuration of output checker email field
- admin interface permits modifying which output checker can see which projects

Review the existing front-end forms, backend API, reporting, downloads, and “my requests” interfaces, then trace current project/group authorization and Keycloak/Active Directory integration. Done means administrators can configure project-specific fields, templates, capabilities, email visibility, and ordering, with changes reflected across the named interfaces.

Written by the indexing model from the issue text.