Copilot configuration for project

[jmgasper]

We ran into a recent situation where a TC admin had set up a project in TC Direct, but that same project also had a copilot that wasn't using TC Direct.

This caused problems because all tickets processed used the TC admin's handle as the copilot value on the tickets instead of the correct copilot.

UI change

To fix this, we can add a new field to the project form (both add and edit) to allow the copilot to be set separately.

By default, when adding a project, this should be set to the username of the logged in user, if they have the copilot role associated with their account. If there is no copilot role associated with the logged in user, we will leave the field blank.

Filling in the Copilot field on the add project form will be required.

Backend change

In addition to tracking the copilot in the UI and DB, we also need to ensure that the configured value is used when creating tickets. Please ensure that when the copilot is set, it is using the configured copilot handle from the DB, not the owner of the project.