remove region env var and retrieve from config instead

[aniruddha2000]

How to categorize this PR?

/kind enhancement

What this PR does / why we need it:

This PR removed the region from the deployment environment variable because CSI retrieves it from config instead.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

should be meged with stackitcloud/cloud-provider-stackit#1244 @breuerfelix

Breaking changes:

[nschad]

Please add a description @aniruddha2000

[nschad]

/hold requires release of new cloud-provider-stackit

[stackit-ske]

Our project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 15d of inactivity, lifecycle/stale is applied
• After 15d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 7d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Mark this PR as rotten with /lifecycle rotten
• Close this PR with /close

/lifecycle stale

[nschad]

/remove-lifecycle stale

[nschad]

/unhold
/lgtm
/approve

[ske-prow]

LGTM label has been added.

Details

Git tree hash: 12fb8aa49e0d2e71c0a2d65ecdebd37967db4338

[ske-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nschad

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [nschad]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[nschad]

/override pull-gardener-extension-provider-stackit-integration-tests

[ske-prow]

@nschad: Overrode contexts on behalf of nschad: pull-gardener-extension-provider-stackit-integration-tests

Details

In response to this:

/override pull-gardener-extension-provider-stackit-integration-tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.