Add specific tolerations to calico-typha pods

[nojnhuh]

What type of PR is this?
/kind flake

What this PR does / why we need it:

This is the same problem as #5703 but for calico-typha pods, with the same fix as #5704.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

TODOs:

• squashed commits
• includes documentation
• adds unit tests
• cherry-pick candidate

Release note:

NONE

[nojnhuh]

/test pull-cluster-api-provider-azure-capi-e2e

[nojnhuh]

/hold to get a few runs of the test in

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 53.08%. Comparing base (578a274) to head (c22e904).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5819      +/-   ##
==========================================
+ Coverage   53.06%   53.08%   +0.01%     
==========================================
  Files         279      279              
  Lines       29678    29687       +9     
==========================================
+ Hits        15750    15759       +9     
  Misses      13112    13112              
  Partials      816      816              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[nojnhuh]

/test pull-cluster-api-provider-azure-capi-e2e

[k8s-ci-robot]

@nojnhuh: 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-cluster-api-provider-azure-conformance-with-ci-artifacts	c22e904	link	false	/test pull-cluster-api-provider-azure-conformance-with-ci-artifacts

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

[nojnhuh]

#5686

/test pull-cluster-api-provider-azure-capi-e2e

[nojnhuh]

/test pull-cluster-api-provider-azure-capi-e2e

[nojnhuh]

/test pull-cluster-api-provider-azure-capi-e2e

[jackfrancis]

I've seen enough

/lgtm
/approve
/hold cancel

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: c52a4a48eefd0f972cdbe07ae58fe0091d01abc6

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jackfrancis

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 [jackfrancis]

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