fix nil pointer in front loadbalancer creator

[xrstf]

What does this PR do / Why do we need it:
Defaulting the annotations map happened too late, leading to possible nil pointer panics when custom annotations are configured (a common scenario).

Does this PR introduce a user-facing change?:

Fix handling custom annotations for the front-loadbalancer Service

[kubermatic-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xrstf

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:

• pkg/resources/OWNERS [xrstf]

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

[xrstf]

/cherrypick release/v2.20

[kubermatic-bot]

@xrstf: once the present PR merges, I will cherry-pick it on top of release/v2.20 in a new PR and assign it to you.

In response to this:

/cherrypick release/v2.20

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.

[kubermatic-bot]

LGTM label has been added.

Git tree hash: 0f70b00a00da5532dafd5687689d6d714910e8e8

[embik]

/retest

[kubermatic-triage-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs

Review the full test history

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[kubermatic-bot]

@xrstf: new pull request created: #10437

In response to this:

/cherrypick release/v2.20

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.