stx-tools: minikube profiles interfere with each other

[Davlet Panech]

Brief Description
-----------------
Helm doesn't work correctly with minikube when there are multiple running profiles.

Severity
--------
Critical

Steps to Reproduce
------------------
* Stop all minikube profiles using "minikube profile list" and "minikube profile stop $PROFILE"
* Create 2 different project environments using minikube.
* Enter the 1st environment and start it (stx-init-env)
* In 1st environment, check helm chart status ("stx control status")
* Start the 2nd environment and start it
* In 2nd environment, check helm chart status ("stx control status")
===> Command returns empty list (no pods etc)
* Go back to the 1st environment and check helm chart status again
===> Command shows pod errors

Expected Behavior
------------------
Environments should remain completely independent and all helm & "stx control" commands should work as expected.

Actual Behavior
----------------
Helm-related commands interfere between environments.

Reproducibility
---------------
Reproducible

System Configuration
--------------------
N/A

Branch/Pull Time/Commit
-----------------------
master 2023-02-08
r/stx.8.0 2023-02-08

Last Pass
---------
Never

Timestamp/Logs
--------------
N/A

Test Activity
-------------
N/A

Workaround
----------
None

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/tools/+/873161

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: r/stx.8.0
Review: https://review.opendev.org/c/starlingx/tools/+/873167

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/tools/+/873161
Committed: https://opendev.org/starlingx/tools/commit/714bb7cbf677d703b85f81a4361b02e8b348eeb8
Submitter: "Zuul (22348)"
Branch: master

commit 714bb7cbf677d703b85f81a4361b02e8b348eeb8
Author: Davlet Panech <email address hidden>
Date: Wed Feb 8 12:36:49 2023 -0500

    Avoid minikube profile interference

    The "stx" script calls helm without specifying which minikube profile to
    use, so it ends up using whichever profile was started last.

    TESTS
    =============================
    * Create 2 different build environments
    * Make sure "stx-init-env" and "stx control start/stop/status" don't
      interfere with each other in different environments

    Closes-Bug: 2006622
    Signed-off-by: Davlet Panech <email address hidden>
    Change-Id: Ic92d7792f4a1baf374e9e8ce25b88d6aee7d2b62

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/tools/+/873167
Committed: https://opendev.org/starlingx/tools/commit/a1a02a7373515761c98da01191df1180e05c29d3
Submitter: "Zuul (22348)"
Branch: r/stx.8.0

commit a1a02a7373515761c98da01191df1180e05c29d3
Author: Davlet Panech <email address hidden>
Date: Wed Feb 8 12:36:49 2023 -0500

    Avoid minikube profile interference

    The "stx" script calls helm without specifying which minikube profile to
    use, so it ends up using whichever profile was started last.

    TESTS
    =============================
    * Create 2 different build environments
    * Make sure "stx-init-env" and "stx control start/stop/status" don't
      interfere with each other in different environments

    Closes-Bug: 2006622
    Signed-off-by: Davlet Panech <email address hidden>
    Change-Id: Ic92d7792f4a1baf374e9e8ce25b88d6aee7d2b62
    (cherry picked from commit 714bb7cbf677d703b85f81a4361b02e8b348eeb8)