fix(picker-column): column renders correctly with selected value

[sean-perkins]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

The picker column is mutating the reference object for the column options. This causes the check that compares the transform value against the option's transform value, to skip applying the button transform values and the column items will overlap (on the second open with a selected value).

Issue URL: #17664

What is the new behavior?

• Always apply the button transform for the option.
• Picker renders correctly with a selected value.

Does this introduce a breaking change?

• Yes
• No

Other information

Main	PR
Kapture.2022-03-23.at.19.54.16.mp4	Kapture.2022-03-23.at.19.53.18.mp4

[liamdebeasi]

Looks good. Can we post a dev build on the issue thread and collect feedback prior to merging?

[averyjohnston]

LGTM once the below comment is addressed 👍

[gee1k]

Thank you for your hard work! i need it, Please merge it

[liamdebeasi]

@sean-perkins We can merge this once the branch is synced with main. I think we gave developers plenty of times to test, and both Amanda and I have found no issues with the PR.