The resources.limits.memory unit is automatically converted. Why cannot the unit be displayed as configured?

### What happened?

When resources.limits.memory is set to 1237.3Mi, the actual pod is 1297403084800 m by running the kubectl command, which is difficult to understand.

### What did you expect to happen?

Resources.limits.memory can be displayed based on the configured value and unit.

### How can we reproduce it (as minimally and precisely as possible)?

Set resources.limits.memory to 1237.3Mi and run the kubectl command to check the value.

### Anything else we need to know?

_No response_

### Kubernetes version

```console
$ kubectl version
# paste output here
```
1.31

### Cloud provider

### OS version

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

### Install tools

### Container runtime (CRI) and version (if applicable)

### Related plugins (CNI, CSI, ...) and versions (if applicable)

Start by reproducing the issue with resources.limits.memory set to 1237.3Mi, then run the kubectl command described in the report and trace where the configured quantity is converted for display. Done means kubectl presents the memory value in the configured unit rather than only the converted integer value.

Written by the indexing model from the issue text.