devicemanager: add timeout for GetPreferredAllocation and Allocate RPC

[ytinirt]

What type of PR is this?

/kind bug

What this PR does / why we need it:

For devicemanager, add timeout for GetPreferredAllocation and Allocate RPC, like PreStartContainer already does.

Make sure not stucking in those RPC, otherwise all new coming pods would be blocked on admitting.

Which issue(s) this PR fixes:

Fixes #129249

Special notes for your reviewer:

Timeout for GetPreferredAllocation and Allocate RPC is consistent with PreStartContainer, which takes 30 seconds.

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Hi @ytinirt. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ytinirt
Once this PR has been reviewed and has the lgtm label, please assign klueska for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• pkg/kubelet/cm/OWNERS
• staging/src/k8s.io/kubelet/OWNERS

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

[JornShen]

/ok-to-test

[ffromani]

/triage accepted
/priority important-longterm

[ffromani]

Hi, thanks for the fix.
The fix per se is straightforwarded and much needed. I have 2 concerns here:

1. (very) minor: I'm skeptical about per-call timeout constants, which incidentally all have the same value. I would have started with a single common value and then differentiate per call if/when needed, but this ship has sailed so be it
2. major: the fix in isolation LGTM, but the problem here is "in isolation". We need to check if something else somewhere breaks, and for this we can use unit and e2e tests, especially the latter. However the latter may turn to be a quite deep rabbit hole, because this area is unfortunately not extensively covered by e2e tests. But we can start anyway.