topology-aware: CPU reservation by resource.Quantity always rounded up to next integer

### Bug Description

Partial CPU reservation alway accounted as the rounded up next integer amount. For instance a 750m reservation will effectively reserve a full CPU.

### Expected behavior

Container allocations not in the kube-reserved namespace should not get rejected if the non-reserved portion of CPU has not been fully exhausted by non-kube-system containers.

### Experienced behavior

750m reservation is accounted as 1000m.

### Steps to reproduce the behavior

Steps to reproduce the behavior
1. Reserve 750m CPU
2. Create container with ($available - 750m) CPU request

### Environment

_No response_

### Additional context

Additional information about the bug