feat: add global copyable IDs and stabilize e2e flows

[Baluduvamsi2006]

Why submit this pull request?

• Bugfix
• New feature provided
• Improve performance
• Backport patches

What changes will this PR take into?

This PR introduces global one-click copy-to-clipboard support for key resource identifiers and includes related e2e reliability fixes.

1. Added a shared copyable text component and reused it across target list pages and plugin card display.
2. Enabled copy UX for IDs/usernames in multiple resource list views to provide consistent behavior.
3. Added i18n entries for copy tooltip/success text in English, Chinese, Spanish, German, and Turkish.
4. Normalized copied values with string conversion where needed to avoid non-string edge cases.
5. Fixed Windows e2e path handling by switching file URL path resolution to a cross-platform-safe approach.
6. Stabilized e2e upstream TLS Verify interaction by toggling through a visible, reliable control path.

Checklist:

• Did you explain what problem does this PR solve? Or what new features have been added?
• Have you added corresponding test cases?
• Have you modified the corresponding document?
• Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

Notes:

• Existing e2e coverage was used and related e2e helper/spec behavior was updated for stability.
• No backward-incompatible API or contract changes are introduced.

[Baluduvamsi2006]

@Baoyuantop , could you please review this PR when you have time?

I also included e2e stability fixes in this PR. Without these fixes, path-resolution issues and flaky UI interactions in the e2e helpers made it difficult to identify true pass/fail results. I fixed those issues in the same PR so the test output is now reliable and actionable.

[Baoyuantop]

The CopyableText abstraction for reuse is a good direction. A few items to address:

1. Issue reference: #0001 in the PR description is a placeholder. Please link the actual related issue(s).

2. e2e interaction: The TLS Verify switch uses evaluate(click) which bypasses Playwright's normal visibility/actionability checks. Please use getByTestId + standard click instead. If evaluate is necessary, please document why.

3. PR scope: Mixing feature work (copyable IDs) with e2e stability fixes in one PR creates coupled merge decisions and coarse rollback granularity. Please consider splitting into two PRs.

4. Component testing: Please add at least one component-level test for CopyableText (successful copy / empty value / failure branch).