CST - update CST workspace component-library from version 43.0.2 to 48.0.2 due to upload …

[pmclaren19]

Summary

We created a workspace in https://github.com/department-of-veterans-affairs/vets-website/pull/33036 pr but the changes were not being merged into Staging.

Found this platform doc about workspaces and realized we were missing our dependency in the nohoist section so we added that but we still weren't seeing our changes in staging.

After investigating @micahchiang found that the component-library 43.0.2 version that we were setting in the workspace was being overridden buy the root folder and we needed to update content-build for the claim status app to have "useLocalStylesAndComponents": true so the version in our workspace was being used so we did that here.

Tested these changes and found that when uploading a .txt file or .jpg file it is adding it as a .pdf file for some reason.

https://github.com/user-attachments/assets/d5311601-705b-473f-81a8-f455c6306853

https://github.com/user-attachments/assets/bc121a8d-4354-45e9-a39d-701e576f0ebd

Since this seems like a larger issue then the initial bug and I am unable to reproduce this bug in my dev env created this ticket to roll our workspace version of the component-library back to 48.0.2

Related issue(s)

• _Link to ticket created in https://github.com/department-of-veterans-affairs/va.gov-team/issues/96817
• _Link to previous change of the code/bug https://github.com/department-of-veterans-affairs/vets-website/pull/33036
• _Link to previous change of the code/bug https://github.com/department-of-veterans-affairs/vets-website/pull/33074
• _Link to previous change of the code/bug https://github.com/department-of-veterans-affairs/content-build/pull/2361

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

Note: This field is mandatory for UI changes (non-component work should NOT have screenshots).

	Before	After
Desktop

What areas of the site does it impact?

(Describe what parts of the site are impacted if code touched other areas)

Acceptance criteria

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

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

[pmclaren19]

After further investigation found that this issue is a backend thing and was happening before our initial changes with this ticket so we do not need to roll the component-library back. The Light house API updates files received to be pdfs. Closing this ticket.