Optimize veda-ui library bundle size

[dzole0311]

Context

The published veda-ui library bundle size has increased. Part of this is the copying of assets such as USWDS images and fonts during the library build process. These assets (like the images) are needed especially for the legacy instances like veda-config that doesn't use USWDS as a dependency unlike the new instances (#1389). There’s room for optimization here, including removing unused assets or modules from the existing veda-ui (e.g. air-quality-and-covid-19--story-cover.png etc) or installing USWDS in the legacy instances (e.g. potential outcome of #1389)

Acceptance Criteria

• Given when then
• Given when then

Related Tickets

[If applicable, link any tickets that are related]

[hanbyul-here]

👋 Thanks for creating the ticket! Since I was thinking about a related issue...

• Library is outputting unnecessary assets (like e.g. air-quality-and-covid-19--story-cover.png This is related to the third item in this ticket: Streamline Package Release, Code cleanup and Next.js Deployment related to refactoring #1360 (comment))
• If the assets are not used with registry anyway, is this something that can be done by streamlining how we build for submodule vs. registry?
• I was also just thinking we might want legacy instances to have uswds as a dependency!