Clean up documentation of new-er `--report` spec that include triggers, etc

[timsnyder]

map/sparta/src/CommandLineSimulator.cpp

Lines 1482 to 1484 in 72ce0f0

	oss << "Please refer to the files 'ReportTriggers.txt' and 'SubreportTriggers.txt'" << std::endl;
	oss << "found in this directory for more information on how to specify these options" << std::endl;
	oss << "from YAML files directly." << std::endl;

I recently ran into this error message. The in this directory part is really confusing. Should it point to the Sparta documentation somewhere instead?

Nope, the files to which it refers are in the CoreExample directory.

• https://github.com/sparcians/map/blob/2adb7106789eccc22b9a2b4e311b14905a741b96/sparta/example/CoreModel/ReportTriggers.txt
• https://github.com/sparcians/map/blob/2adb7106789eccc22b9a2b4e311b14905a741b96/sparta/example/CoreModel/SubReportTriggers.txt
• Also looks like there are copies in https://github.com/sparcians/map/blob/2adb7106789eccc22b9a2b4e311b14905a741b96/sparta/example/DynamicModelPipeline/

Not intuitive at all when one encounters this in the wild as a result of passing old arguments to an actual Sparta-based simulator that has nothing to do with the CoreExample.

What's worse is that the new hierarchical report specification seems to only be documented in those TXT files in the core example, it isn't included in the doxygen. Also, highly confusing.

[klingaard]

Seems like an easy fix. Also, didn't know those files existed. Will do this:

1. Move these files to sparta/doc/sparta_docs and remove dups
2. Proof read and fix anything that's wrong.
3. Connect it in with the existing documentation.