Added checks for non-gardener managed seed clusters to ensure correct seed configurations.

[ScheererJ]

How to categorize this PR?

/area networking
/area quality
/kind technical-debt

What this PR does / why we need it:
Added checks for non-gardener managed seed clusters to ensure correct seed configurations.

Clusters managed by gardener embed information about the node, pod and service networks inside the cluster as a config map. Other kubernetes clusters do not offer this information in a standard way.
To ensure that the seed configuration fits to the reality of the seed cluster this change introduces a heuristic check that the configured node network is valid for the nodes seen in the cluster. The same applies to the pods and services. (The amount of entities being checked is limited so that large clusters do not delay the gardenlet start-up too much.)

Which issue(s) this PR fixes:
None.

Special notes for your reviewer:
Having the seed configuration diverge from the seed cluster reality can lead to hard to track down issues with network policies as some of the ranges are taken from the seed configuration.

Release note:

Gardenlet will not start in case the seed configuration is incorrect, i.e. if the node, pod or service network specified in the Seed resource do not match to the cluster reality.

[rfranzke]

/assign

Thanks, looks good, just a few nits

[gardener-prow]

@ScheererJ: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-gardener-check-vulnerabilities	113755b	link	false	/test pull-gardener-check-vulnerabilities

Full PR test history. Your PR dashboard. Command help for this repository.
Please help us cut down on flakes by linking this test failure to an open flake report or filing a new flake report if you can't find an existing one. Also see our testing guideline for how to avoid and hunt flakes.

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/test-infra repository. I understand the commands that are listed here.

[rfranzke]

/lgtm
/approve

[gardener-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rfranzke

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rfranzke]

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