Remove tempest container support from Wallaby release

[chandan kumar]

During Queens release, since all the services shipped are containerized.
So, we also shipped tempest in a container.
Earlier we used to test tempest container in tripleo ci jobs using tripleo-quickstart-extras validate-tempest ansible role but from last 1 year,
we worked very hard to consolidate tempest execution/configuration/post-processing via new
Ansible role openstack-ansible-os_tempest adopted from OpenStack Ansible team.

This role is so extensible that it solved all the use cases related to tempest.

Due to this, we are deprecating the validate-tempest role this year and tempest container is no longer used and tested in CI.

From Queens to till now, we have received doc bugs related to the tempest container and the tempest container contains so many hacks to run it. It is very hard to maintain.
There are no users we have seen, so we are removing the tempest container.

Here is the tripleo-common patch for Removing tempest container build:
https://review.opendev.org/c/openstack/tripleo-common/+/771993 and announcement to openstack-discuss list: http://lists.openstack.org/pipermail/openstack-discuss/2021-January/020059.html

Here is the RH bugzilla for tracking the same: https://bugzilla.redhat.com/show_bug.cgi?id=1926863

[Marios Andreou (marios-b)]

https://review.opendev.org/c/openstack/tripleo-heat-templates/+/776615 Remove tempest container support from tht

[Marios Andreou (marios-b)]

also these

        * Removing tempest container build
        * Change-Id: I4dc869019a04bf092f8c219e470be55f3bc682d3
        * https://review.opendev.org/c/openstack/tripleo-common/+/771993

        * Remove enable_tempest flag from tripleoclient
        * Change-Id: I2e2c126aa95589a8d26eaec9626abbf4a86044ca
        * https://review.opendev.org/c/openstack/python-tripleoclient/+/776654