consider extracting a peer results workflow into a new/separate repo

[cjyetman]

As far as I understand, we currently use this repo for:

• generating data files needed for the meta report
• generating the peer results files that need to be added to the "pacta-data" that currently get bundled into each Docker image
• running large numbers of portfolios for specific projects that are not using TM

Though we may need to consider how to share the queuing infrastructure so we're not maintaining multiple discreet versions of it, it may be advantageous to separate out the different use cases into use-specific workflows. That way, for example, the peer results workflow could maybe be integrated into an umbrella data.prep workflow that preps the data, then runs the indices portfolios through PACTA analysis to get the benchmark files, and also runs the peer portfolios for appropriate initiatives through PACTA analysis to generate the peer files that are needed for a fully complete "pacta-data" set ready to integrate into a new Docker image.

[jdhoffa]

Deserves further consideration/ attention.

One quick note, the azure related queuing infrastructure lives here: https://github.com/RMI-PACTA/azure-pacta-runner (and this depends on workflow.meta.data.creator)