Under the hood
Sandbox AWS credential-collision handling was renamed internally with no functional change found
What
The logic that decides which AWS access-key/secret/session credential pair wins when multiple environment variables collide (the credentials.awsPairs resolution logic) is still present with the same warning messages, just with renamed internal variables.
Why
This is internal cleanup only; the previously reported behavior for dropping conflicting AWS credential pairs is unchanged.