export env variables required to run onboarded apps p2p makefile targets

[tombart]

new functionality that allows to export required env variables required to execute onboarded apps p2p make targets issue: https://github.com/coreeng/project-platform-accelerator/issues/396. The command will print out export statements in new lines as:

export BASE_DOMAIN="gcp-dev.cecg.platform.cecg.io"                                 
export REPO_PATH="../tombart-app"                                                  
export REGION="europe-west2"                                                       
export REGISTRY="europe-west2-docker.pkg.dev/core-platform-efb3c84c/tenant/tomaszb"
export VERSION="53b9c85"                                                           
export TENANT_NAME="tomaszb" 

The user is expected to copy and paste in terminal.

Example run: corectl p2p export --tenant tomaszb --environment gcp-dev --repoPath ../tombart-app or corectl p2p export --tenant tomaszb --environment gcp-dev -- defaults to current dir or eval $(corectl p2p export --tenant tomaszb --environment gcp-dev --repoPath ../tombart-app) -- automatically add vars to current shell

There is quite a lot of duplication in the tool in both logic and code, however due to the size of this pr didn't do much cleanup. Probably better to tackle separately as sep tickets. Also p2p sync command is quite similar to this one, however not very extensible to be re-used. Would need to major refactoring which decided not to do as a part of this work.

[tombart]

I was under impression that this command will be using information from remote repository. I.e. if I do corectl p2p export -r <path_to_app> it will not ask me about tenant but will get it from repo variable TENANT_NAME

As for the environments (as there may be muliple existing per repo) we could make user choose, but only from the ones that exists in repo, i.e. gcp-prod, gcp-dev

As agreed with Tiago/Lukasz:

• we'll construct export vars based on local configuration, this is mainly due to extra permission tenant would need for each repo to view gh action environments, constructing from local config won't need that permissions
• tenant flag is still required and in interactive mode load all tenants for user to pick
• filter all environments based on tenant provided and present only tenant onboarded envs (in interactive mode)