[CST] - Changes text and link on the Copy of Exam component

[pmclaren19]

Summary

User wrote in that they had a HLR and the sidebar content with the header Want a copy of your claim exam? had a text that was inaccurate. Updated the text to be accurate per @jstrothman guidance, added a new link to https://va.gov/find-forms/about-form-20-10206/, increased top heading padding to 40 px and added tests.

Slack Convo regarding this change and verification of changes - https://dsva.slack.com/archives/C04KHCT3ZMY/p1732207071698879

Related issue(s)

• Link to ticket created in va.gov-team repo department-of-veterans-affairs/va.gov-team#97601

Testing done

• Describe what the old behavior was prior to the change
• Describe the steps required to verify your changes are working as expected
• Describe the tests completed and the results
• _Exclusively stating 'Specs and automated tests passing' is NOT acceptable as appropriate testing
• Optionally, provide a link to your test plan and test execution records

Screenshots

	Before	After
Desktop

Video of new experience:

https://github.com/user-attachments/assets/5b48a205-16c3-452e-a480-e0fdf863440f

What areas of the site does it impact?

Claim Status Tool

Acceptance criteria

• [x] In Claim Status Tool, change content to match the language provided under Change to make in this ticket
• [x] Reply in this ticket re what claim types show this information. This info is for reference later, and won't change the work in this ticket.
• [x] Add a top margin of 40px to the 'Want a copy of your claim exam?' header

Quality Assurance & Testing

• [ ] I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• [ ] No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• [ ] Linting warnings have been addressed
• [ ] Documentation has been updated (link to documentation *if necessary)
• [ ] Screenshot of the developed feature is added
• [ ] Accessibility testing has been performed

Error Handling

• [ ] Browser console contains no warnings or errors.
• [ ] Events are being sent to the appropriate logging solution
• [ ] Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• [ ] Did you login to a local build and verify all authenticated routes work as expected with a test user