fix(web): copy code component accessibility

[yanthomasdev]

This PR adds screen reader-only text to the copy-code.tsx component with aria-live to give feedback once the content is copied.

This is meant to make it compliant with WCAG's Success Criterion 1.1.1: Non-text Content (Level A), ensuring the button's purpose and state, represented by an icon, can be understood by users of assistive technologies.

Changes were tested on Windows 11, Chrome, NVDA. For reference, before the announcement would be "button", now "button, copy to clipboard" and "copied" after clicked.

I haven't opened an issue since it wasn't clear if they should be opened for issues/bugs outside the library itself. Let me know if one's necessary.

---

Summary by cubic

Adds a screen reader–only live region to the copy-code button so assistive tech announces “Copy to clipboard” and “Copied.” This clarifies the button’s purpose and state and aligns with WCAG 1.1.1.

^{Written for commit 4f7cb18. Summary will update on new commits.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4f7cb18

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@yanthomasdev is attempting to deploy a commit to the resend Team on Vercel.

A member of the Team first needs to authorize it.

[cubic-dev-ai]

No issues found across 1 file

[yanthomasdev]

Look like community PRs need approval in the Vercel dashboard to be deployed, I think they do have options to make it more flexible. Let me know if I can help somehow.

[gabrielmfern]

@yanthomasdev not waiting for the deployments, they shouldn't be required to merge, just CodeQL and cubic that are just not running for some reason

[yanthomasdev]

@gabrielmfern oh, I have an idea what might be the issue. Could you take a look at the branch protection rules? Since it only affected me (contributor) but doesn't seem to affect you and other maintainers (that might be able to bypass branch protection rules) depending on the branch, it might be because it requires some workflow to run that doesn't exist anymore.

Here's a GitHub discussion on this issue: https://github.com/orgs/community/discussions/26698

[gabrielmfern]

@yanthomasdev yeah I think it's something along those lines, maybe because those two workflows only run for maintainers, I'll take a look, for now I've removed the requirement for them to succeed before merging