refactor(cloud-native): revisit Python libs installation method

[iromli]

Prepare

• Read PR guidelines
• Read license information

---

Description

Target issue

closes #8553

Implementation Details

• Keep python3 package.

• Keep libs that require native library, e.g. py3-grpcio, py3-cryptography, py3-psycopg2 to avoid the complexity of building native packages.

• Rename EXTERNALLY-MANAGED file as the side-effect of missing the file is low.

  A distro Python when used in a single-application container image (e.g., a Docker container). In this use case, the risk of breaking system software is lower, since generally only a single application runs in the container, and the impact is lower, since you can rebuild the container and you don’t have to struggle to recover a running machine. There are also a large number of existing Dockerfiles with an unqualified RUN pip install ... statement, etc., and it would be good not to break those. So, builders of base container images may want to ensure that the marker file is not present, even if the underlying OS ships one by default.

  In certain contexts, such as single-application container images that aren’t updated after creation, a distributor may choose not to ship an EXTERNALLY-MANAGED file, so that users can install whatever they like (as they can today) without having to manually override this rule.

• Uninstall pip3 and wheel libs.

---

Test and Document the changes

• Static code analysis has been run locally and issues have been fixed
• Relevant unit and integration tests have been added/updated
• Relevant documentation has been updated if any (i.e. user guides, installation and configuration guides, technical design docs etc)