CQF tooling- align file naming convention for compatibility with FSH resources

[costateixeira]

when the tool writes out the json files, it should be able to merge them with the fsh-generated resources, but for this we need a simple change:

• save the resources in the output folder (given by an argument) prepending the resource type and a dash, but not under a folder with the resource type name - i.e. output files as <resourcetype>-<name>.

For example:
When the arguments include -lop ./fsh-generated/resources -mop ./fsh-generated/resources -rp ./fsh-generated/resources
the Measure resource MERTXCURR can be found in the file
./fsh-generated/resources/Measure-MERTXCURR.json
AND should be output to the same file
(currently the tooling saves under
./fsh-generated/resources/measure/Measure-MERTXCURR.json
)

Presuming this is a simple change that requires no further refactoring, I understand it will allow us to finally integrate this with the standard FHIR tooling.

I can setup a branch with a (failing) test if needed, consisting of the template changes

[costateixeira]

update: seems the folder is defined in IGProcessor.java, and if we can set the arguments to e.g.
public static final String libraryPathElement = "fsh-generated/resources/";
this may be an option (simpler?)
What seems to be needed with this option is then to prepend the filename with the resource type.

[brynrhodes]

There's actually a lot that would need to be updated to accomplish this, but the starting point would be here in the RefreshIGParameters processing:

https://github.com/cqframework/cqf-tooling/blob/master/tooling/src/main/java/org/opencds/cqf/tooling/operation/RefreshIGOperation.java#L28

You could take a first pass by just setting the libraryOutputPath and measureOutputPath parameters and see how far you get, that might actually work for IGs that only have Libraries and Measures.

[costateixeira]

https://chat.fhir.org/#narrow/stream/215610-shorthand/topic/Output.20file.20naming.20convention