Make `dev-pulumi` to deploy all our "Tools" like Jenkins / SonarQube to k8s. Any change in `dev-pulumi` repo `master` branch should automatically trigger redeploy of our "Tools" to k8s cluster

How it should be working:
- DevOps engineer clones this repo to her/his PC
- create `.env` file locally on his PC (in root of this repo, ignored in Git!) which describes all secret API keys which will be needed for all infra/apps (e.g. Github Token for pushing of packages to Github packages store, AWS Secret / API key, and many others).
- switch (optionally) to the required stack in Pulumi with `pulumi stack select xxx`, where xxx is the name of env (e.g. dev, prod, stage). We may have different env configurations, depending of the stack (e.g. in production we can use more powerful k8s cluster)
- run `pulumi up`
- enjoy all software provision ino the relevant AWS resources (e.g. AWS EKS cluster)

Start by reviewing the dev-pulumi repository's Pulumi configuration and the required .env and stack-selection flow. The work is done when pulumi up provisions the relevant AWS resources and Tools on Kubernetes, and changes to the master branch automatically trigger redeployment.

Written by the indexing model from the issue text.