[CST] - Updated Documents Filed so that the documents are sorted correctly

[pmclaren19]

Summary

• Updated DocumentsFiled.jsx so that the logic accounts for trackeditems having multiple documents and the document upload date being different then that of the tracked items
• When there is an uploadDate in the trackedItems documents, we will sort on the date of the first document and use that as the date that is shown instead of the trackedItem date
• Added a test to DocumentsFiled.unit.spec.jsx around the above scenario

Related issue(s)

• Link to ticket created in va.gov-team repo
  [bug][CST] Documents filed sorting issue va.gov-team#81756

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
Documents Filed List

What areas of the site does it impact?

Claim Status Tool

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

⚠️ Team Sites (only applies to modifications made to the VA.gov header) ⚠️

• The vets-website header does not contain any web-components
• I used the proxy-rewrite steps to test the injected header scenario
• I reached out in the #sitewide-public-websites Slack channel for questions

[jerekshoe]

I think the icon value here needs to be updated. Also use class instead of className for web components

[pmclaren19]

I never intended to update the icon so not quite sure how this got added, rolling it back to what it was.