Improving CI/CD on FNNDSC repositotires

This is the ticket to manage the activities to improve CI/CD across the FNNDSC repositories.

@BillRainford will take it.

Here is the email I sent him the following email on Sep 3.
Feel free to update your status here.
As I am not sure what the goal of this ticket is, we need to clarify it.
Thanks!

```
The target repositories for the CI/CD work is the every repository in
https://github.com/FNNDSC .
Right now 256 repositories.

Do not worry. We can have a priority for repositories that we work on.

Right now here is the priority as a result we just discussed casually.
But you can change or see your own priority on the list by checking it
by yourself, or communicating with stakeholders.

1. https://github.com/FNNDSC/ChRIS_ultron_backEnd
2. https://github.com/FNNDSC/ChRIS_ui
3. https://github.com/FNNDSC/ChRIS_store
4. https://github.com/FNNDSC/ChRIS_store_ui

https://github.com/FNNDSC/pl-* are the ones of the plugin.

Possibly Travis CI is used for CI right now.
And some of CIs used for a pipeline to do something, not only for a test.

For 1. ChRIS_ultron_backEnd, there is only one job case.
https://github.com/FNNDSC/ChRIS_ultron_backEnd/blob/master/.travis.yml
As a personal opinion, I want to see our currently supported cases
(Ubuntu, MacOSX, Docker) and a new supported case (Fedora, Podman) are
covered.
https://github.com/FNNDSC/ChRIS_ultron_backEnd#install-latest-docker-and-docker-compose
```