fix custom assetFileNames issue

[apatel369]

Changes

closes #426 in adapters repo

When using custom assetFileNames in Astro configuration assets were incorrectly moved to the server directory instead of the client directory. This caused 404 errors when the browser tried to load these assets from the client side.

Users could specify custom directories for various asset types (e.g., CSS, images). To handle that used asset paths from the build output to ensure assets are moved from/to the correct directories.

Testing

Added tests for testing image and CSS assets with custom paths.
The previous test was passing cause accidentally build.assets and custom assetFileNames path were matching.
(assets and assets/css)
So updated that as well.

Docs

N/A bug fix

[changeset-bot]

⚠️ No Changeset found

Latest commit: b07ac29

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codspeed-hq]

CodSpeed Performance Report

Merging #12449 will improve performances by 19.02%

_{Comparing apatel369:arpan-#426-adp-customfilename (c5ac0ab) with main (350b3da)}

Summary

⚡ 1 improvements
✅ 5 untouched benchmarks

Benchmarks breakdown

	Benchmark	main	apatel369:arpan-#426-adp-customfilename	Change
⚡	Rendering: streaming [true], .mdx file	920.9 ms	773.7 ms	+19.02%

[ematipico]

Thank you @apatel369, sorry for the late review. The fix looks good, I would suggest a better description for merging the PR