Implement YAML-based "auto-export" replacement for dev

The current auto-export feature consumes a configuration with a list of paths to export and the corresponding maven module paths, a list of paths to exclude, and a list of paths that require special UUID processing. The output is a set of XML files for the v<=11 bootstrap system.

This feature will replicate the benefits of auto-export using our new YAML-based bootstrap system and workflow. The expected output will be a set of YAML + binary files that will reliably reproduce the current effective JCR configuration nodes when applied on top of the config layers below/before the specified output modules as specified in the stored baseline. This is essentially the same computation as REPO-1684, but ignoring the specified modules from the baseline.

Additionally, a best effort should be made to produce stable output and output that matches the baseline to minimize file-level diff. For example, output should be rendered to the same filenames and in the same text order as similar data in the baseline.

It is acceptable to restrict this feature to operate only on modules within the same config group and to require that these modules have no additional modules depending upon them.