feat(csp): track client scripts and CSS

[ematipico]

Changes

• This PR adds tracking for client assets generated during the build. We already have internals.staticFiles, however it's used for something else, so in order to avoid conflicts, I decided to track these files in a new type. This type then used inside the track* functions inside csp/common.ts
• I removed the need to create the hashes in the prebuild.js script. Turns out there's no need, and we can import the built files during the tracking of the hashes. This simplifies the implementation a lot, because we don't need to rely on two functions to create the digest
• The generation of the hashes now uses the standard crypto from core/encryption.ts. This should avoid possible regressions where node:crypto isn't available in certain runtimes such as edge.
• The file packages/astro/src/core/astro-islands-hashes.ts was removed from git because it's auto-generated and it changes based on the used command (pnpm dev VS pnpm build)

Testing

I tested this using examplex/framework-react, enabled the experimental release, and made sure it works.

I will create e2e tests later. I still need to tackle view transitions, which might be challenging.

The existing CI should stay green

Docs

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0d2cc7e

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

[ascorbic]

Not tried running it, but code all looks fine