Allow companies to adapt ansible-container in their workflow until official release done

[Voronenko]

ISSUE TYPE

• Feature Idea

As it definitely exists blocking point to perform official release of the ansible-container on pypi, I propose to allow companies to adopt ansible-container as custom pypi build in alternative pypi repositories.

In order to do so, I propose:

1. allow to have conductor images to be provided not only from ansible/conductor ... but also company/conductor docker hub repos...

bakery.py - allow passing custom organization to push images into, so the companies can prepare and push prebaked images to custom docker hub repo.

2. conductor.yml -
   support optional parameter conductor_provider (by default - ansible) to get conductor images to be pulled from custom organization.

At the same time, to minimize breaking changes - convention for conductor image names remains the same.

In that way companies can fork, and support ansible-container in their organization until release schedule of main origin returns to regular.

[Voronenko]

Addressed in #966

Note: as there is some blocker to release to pypi , I am supporting non official preview build, available at
https://pypi.org/project/sa-ansible-container/#description

requirements.txt is the same, just with sa- prefix

sa-ansible-container[docker]