Convert binaries in "source" folders

[costateixeira]

Add support for having source files like gherkin files (which get used in a testplan.testRun.script.sourceReference) as a Binary.
Then these files would be rendered as text, monospaced, possibly with syntax highlighting (using script.language to identify which language)

• We could add an ig parameter to determine what are the "folders" that contain code that creates Binary instances
• The publisher needs to consider these binaries as NOT examples

@brynrhodes - instead of Binary, are there reasons to use Library?

[grahamegrieve]

we already have all this

[lmckenzi]

Jose will work with Bryn on how best to make Gherkin work via this approach - and determine if this approach makes sense in this use-case.

[JohnMoehrke]

I have a sample IG that includes Gherkin. This is an example of an IG that is focused on testing of another IG, a concept that is independent from the current git issue. This IG can be used to see what Gherkin scripts might look like. This IG can also see various ways in which it would be useful to expose the Gherkin script within an IG.

Github - https://github.com/JohnMoehrke/ConsentWithSeg-testing
CI build - https://build.fhir.org/ig/JohnMoehrke/ConsentWithSeg-testing/branches/main/index.html

• Gherkin has a file format, with an extension .feature, and a mime type text/x-gherkin
  • These can be loaded as binary using the normal method of loading a binary
  • a Binary resource load does throw an error in the QA, while still working.
• Gherkin is considered a script that is human readable. Thus it is considered both a test script and a human narrative of that script
• The R5 TestPlan resource could call upon the feature file in multiple ways
  • testCase.testRun.script.sourceString -- no good way to call upon the feature file
  • testCase.testRun.script.sourceReference -- could reference a DocumentReference that pulls in the feature file using the binary method
  • testCase.testRun.script.narrative -- no good way to call upon the feature file
• Gherkin is considered human consumable; thus it is useful to include it in the human narrative -- https://build.fhir.org/ig/JohnMoehrke/ConsentWithSeg-testing/branches/main/testplan.html -- because of this it would be helpful if the narrative could call upon the feature file to be displayed in a code block.

The test IG shows a testPlan with all (many) of the above combinations. Some of these issues are unique to Gherkin, but might still be useful for other things. Some of these issues may be specific to TestPlan resource definition.

[litlfred]

we also have several Gherkin/Cucumber examples we would want to pull into this approach

[JohnMoehrke]

We need .feature file extension added to the acceptable binary file types. as today we get an ERROR

Unknown file type give-consent.feature

I added #930