feat: CopyToClipboard - Allow separate content from text to copy for inline variant

[ernst-dev]

Description

Original customer ask:

As of now, when CopyToClipboard uses inline variant, it will ignore copyButtonText and use textToCopy for both display and copy value.
Make inline variant to have different copyButtonText and textToCopy values like button variant.

Customer usecase:

When you want to display a date with CopyToClipboard, you may want to display the date in localized, readable format but allow copying in language agnostic, timezone agnostic way, for example, UTC format.
It's a problem because as shown in the screenshot, different variants have different icon color and hurts visual uniformity without good reasons.

Main problem:
With any custom implementation, i.e. combining SpaceBetween using the variant="icon" and a string, it will result in a grey icon, this is particularly a problem when used in conjunction with regular inline CopyToClipboard which has a blue icon like inside a SplitPanel with KeyValuePairs.

Solution:
Adds a new property: textToDisplay which allows for specifying a separate display value from the copy value for variant="inline".

This is achieved by assigning a string to textToDisplay and a separate string to textToCopy.

• e.g. a Human readable date/time to display but a timestamp to copy

If content has no value then textToCopy will be displayed instead.

Related links, issue #, if available: n/a
AWSUI-45434
65TZAG3kNuqE

How has this been tested?

• Manual
• Unit

Review checklist

The following items are to be evaluated by the author(s) and the reviewer(s).

Correctness

• Changes include appropriate documentation updates.
• Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
• Changes do not include unsupported browser features, see CONTRIBUTING.md.
• Changes were manually tested for accessibility, see accessibility guidelines.

Security

• If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

• Changes are covered with new/existing unit tests?
• Changes are covered with new/existing integration tests?

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.51%. Comparing base (4e31a2f) to head (30024ce).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3400   +/-   ##
=======================================
  Coverage   96.51%   96.51%           
=======================================
  Files         806      806           
  Lines       23028    23031    +3     
  Branches     7550     7551    +1     
=======================================
+ Hits        22226    22229    +3     
  Misses        795      795           
  Partials        7        7           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ernst-dev]

I believe this is such a large diff because of this change: #3413