fix(pipelines): replace aws_region with region

[cezarmoise]

region is the correct name for that parameter, not aws_region.
No errors happen currently because all params go into a map, and aws_region is just never used.

It has no real consequences, most tests are triggered and given a region.
But in some cases, i.e. native backup, the region must match the bucket defined in the config.

PR pre-checks (self review)

• I added the relevant backport labels
• I didn't leave commented-out/debugging code

Reminders

• Add New configuration option and document them (in sdcm/sct_config.py)
• Add unit tests to cover my changes (under unit-test/ folder)
• Update the Readme/doc folder relevant to this change (if needed)

[fruch]

@cezarmoise where ever the test that needs a specific region is trigger would need to keep that promise.

Why is holding us from duplicating the needed data into more regions ?

We started using multiple regions for performance tests, to avoid the problem of resources (and try to minimize noisy neighbors issues), and the ability to shift those tests into other regions might become important

[cezarmoise]

@cezarmoise where ever the test that needs a specific region is trigger would need to keep that promise.

Why is holding us from duplicating the needed data into more regions ?

We started using multiple regions for performance tests, to avoid the problem of resources (and try to minimize noisy neighbors issues), and the ability to shift those tests into other regions might become important

It doesn't.
It's just that the name aws_region in the pipeline params is wrong, so the jenkinsfile and the jenkins job don't match.
I could just remove the region param altogether, but that would just use the default eu-west-1

[fruch]

LTGM