Add performance testing scripts and job for release workflow

[denis-tingaikin]

Motivation

It'd be very useful to monitor our perfomance metrics on releasing candidates. It could help to catch performance issues.

TODO

• check scrits (AWS2AWS)
• prepare scripts for githunb workflow
• add perormance testing step on releasing (kind2kind)

[d-uzlov]

The action plan:

• Run MSM perf test scripts manually with AWS2AWS scenario
• Add vl3 test
  • Adopt deployment configs from MSM testing ~4h
  • Run the test manually to ensure that it works ~4h
• Add interdomain kernel2wireguard2kernel test
  • Adopt deployment configs from MSM testing ~4h
  • Run the test manually to ensure that it works ~4h
• Add test scripts and deployments to this repo ~2h
• Add CI configs to run test scripts ~2h
• Trigger CI testing to ensure that everything works ~1h

Currently our scripts from the MSM performance testing reimplement NSM deploy commands from the deployments-k8s repo.
If we change anything in that repo, we would also need to manually update the scripts.
We can probably avoid it if we reuse generated test deploy golang code that we generate for CI testing. For this we would need to update gotestmd tool to include deployment code decoupled from test code.
At first we will merge current scripts, and later we can start working on improving this.

Performance tests will trigger automatically, along with our current release pipeline, which is triggered by pushes to release/... branches.

At first we will add this into integration-k8s-kind repo.
Later we will evaluate if it would be worth it to enable these tests in other integration repositories.

[denis-tingaikin]

Seems like done