add env var to disable tunnel in calico node

Description

When the env var CALICO_DISABLE_TUNNEL is set, the process allocate-tunnel-addrs is not started.

In our environment, we only use BGP, didn't use tunnel, we found when create/delete/update a IPPool, all calico-node will get and update node many times, it will make k8s apiserver load very high.Even if the Typha component is deployed, these problems cannot be alleviated. We have also noticed that there is already an environment variable CALICO_DISABLE_FELIX that has a similar function. So add an another environment variable CALICO_DISABLE_TUNNEL that can control whether to start the process allocate-tunnel-addrs or not.

Related issues/PRs

Fixs #9394

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

projectcalico / calico