Compute environment reporting

[ChrisKeefe]

Full computational reproducibility requires the ability to assemble functionally equivalent hardware and software environments. We should report compute environments as comprehensively as possible. Basic reporting is possible at this time, but there are significant limitations (e.g. due to lack of available data in provenance, and often barriers in how that data could be captured.) Here's a rough roadmap to better reporting:

• basic report available in reproducibility supplement (e.g. in Replay produces a methods manifest #75 or a dedicated report)
• opportunistic capture of resource allocation details in provenance and reporting of them (e.g. through a slurm interface?) (heavily requested by focus group users)
• comprehensive capture of (non-python) software dependencies Comprehensive package capture of QIIME 2 environments in provenance qiime2#587
• capture of hardware/architecture details (e.g. for identifying architecture-related bugs in Support data integrity bug identification #86 )