Implement one repo per image for docker

[kimwdavidson]

• CLI images
• web images
• browser image
• solr image

[rhabbachi]

Related to https://github.com/NuCivic/dkan_management/issues/338

Current situation and latest progress:

dkan-cli

1. dktl master is using the latest dkan-cli image that has PHP 7.2. dktl 1.x used for dkan classic is not. Working on getting that backported.
2. One of the issues with the backport is drush version available in the container. dkan-classic (ie Drupal 7) is only supported by drush:^8, dkan2-Drupal8 kinda works with drush:^8 but dkan8-Drupal9 requires drush:^10 as per the Drupal Compatibility table

dkan-web
More straightforward. No issue, just updating the PHP dependencies.

browser image
Not sure if we need to do anything since we are using an external image (selenium/standalone-chrome-debug:2.53.1)

solr
Not sure if we need to do anything since we are using an external image (devinci/drupal-solr:3.x)

[rhabbachi]

Status update:

web: New repository created, https://github.com/GetDKAN/dkan-web. Automated build configured in dockerhub https://hub.docker.com/repository/docker/getdkan/dkan-web (Build stuck for an undefined reason, waiting for the build job to be resolved).

cli: Since we need to support different Drush versions depending the Dkan version in play. We now have a classic docker tag that bears Drush version 8 suitable for Dkan classic, while keeping the latest with the Drush version 10 needed for Dkan 2 and Drupal 9.

[rhabbachi]

@fmizzell to review https://app.zenhub.com/workspace/o/getdkan/dkan-cli/issues/1 and the https://hub.docker.com/repository/docker/getdkan/dkan-web repository