CST - Added useLocalStylesAndComponents to the claims-status app

[pmclaren19]

Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.

Summary

We created a workspace in department-of-veterans-affairs/vets-website#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.

Related issue(s)

• _Link to ticket created in [CST] Bug in file upload when replacing one file with another va.gov-team#96817
• _Link to previous change of the code/bug claims status pin to component library 43 vets-website#33036
• _Link to previous change of the code/bug CST - Added changes to the claims status workspace vets-website#33074

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
Mobile
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