Use Case

As a user running in FaaS/containerized environments
I want the client metadata size-limiting logic in makeClientMetadata to reduce fields in the order the MongoDB Handshake spec prescribes
So that the highest-value fields (env.name, os.type) are preserved consistently

User Experience

• The driver should delete container values and platform values in order, before env.name as per the spec
• Impact is all users who supply configuration values that escape the size of the limitedsizedocument used to construct client metdata (minimal, unlikely case)

Dependencies

• Pending addition of env.agent (which has the same field value as env.name): NODE-7666

Risks/Unknowns

• None

Acceptance Criteria

Implementation Requirements

• Truncation order of client metadata should be in-line with the spec. Current implementation is that env.container is deleted after env.name, and os is truncated too-early.

Testing Requirements

• Additional unit tests should be added to the existing truncation tests.

Documentation Requirements

• N/A

Follow Up Requirements

• N/A