VACMS-18269 Remove unused assets

[randimays]

DO NOT MERGE

Doing some extra research to make sure images that aren't explicitly in the content-build code (i.e. cross-referenced in vets-website styles or used by the design system) are not removed. This is a WIP

Summary

Removed unused assets from the content-build assets (and assets-removed) folders.

Related issue(s)

• [BLOCKED] Remove unused assets in content-build va.gov-cms#18269

Testing done

Searched the content-build repo for usage of any of these files. Zero results.

[chriskim2311]

LGTM! Nice clean up

[jamigibbs]

Is there any other way to verify that these files aren't being used besides a code search? Do we have access to analytics or some other kind of reporting that could show traffic requests to these files?

[jamigibbs]

I don't think this sprite sheet should be removed. It's added for the va-icon web component. See this readme for a list of places this file should be active: https://github.com/department-of-veterans-affairs/dst-uswds-compile/blob/main/README.md

[randimays]

@jamigibbs Good callout about the sprite file; I've re-added it. I did find one instance (and there may be a few more) where content-build is referring to vets-website styles for an image that should be in the content-build repo. We have a ticket to straighten out those cross-repo styles (here) that we haven't started yet. We'll definitely need to straighten that out before coming back to this. Other than that, and any design system references, there shouldn't be files out in the ether referring to assets in content-build (and if they are, they need to point to a different image bucket). But I'll have another look and see if I can find any analytics to that effect.

Thanks for the review!

[github-actions]

This PR is stale because it has been open 120 days with no activity. It will receive a stale label every day for 14 days before being closed unless it receives a comment or the stale label is removed.

[randimays]

Bumping to keep this from getting closed