[Feature] cli.py is in mapper plugin, should be in own repo

[krobasky]

What problem(s) do you aim to solve? Need to make a sustainable, stand-alone cilent tool to support model developers in a research arena.

What feature solves it and why?

The tool should use the code that's currently in https://github.com/RENCI/pdspi-mapper-parallex-example/blob/master/cli.py, and should be in its own repository, similar to https://github.com/RENCI/pds-release in order to meet the following requirements:

• Needs to have documentation, including a readme, explaining how to use it
• Needs to have automated unit tests
• Needs to have issues/feature requests for it's own project board
• Needs to have automatic installation script(s) with help
• Needs to have a pointer to the supported pds release (I'm thinking a sub-module that points to the correct pds-release version)

Close the this ticket when:

• cli.py uses the pds api instead of the mapper, fhir server directly (depends on #233
• the above requirements listed in this ticket, above, have been met
• an acceptance tester has accepted it.

This is the final product for #216

[krobasky]

Let's remove this requirement:

• cli.py uses the pds api instead of the mapper, fhir server directly address this instead after closing #253

[krobasky]

cli.py now has it's own repo: https://github.com/RENCI/pds-cli-cp/ But it still doesn't use the pds interface; it instead calls the fhir and mapper plugins directly.

This needs more user feedback before we can finish the redesign.

[krobasky]

It's OK to have cli.py to call the mapper and fhir appliances directly if we create an OMOP mapper because then the mapper/fhir appliances will be generic enough while also specific to the research data warehouse being used by the cli.py program. See #257