Add the deployment_identifier to CSS and JavaScript aggregate hashes

I thought of some drawbacks when writing this up, but also a possibly solution in #3. So unless there's a fatal flaw in #3 I think we should do that.

Is deployment_identifier changing if a site is reinstalled from configuration?

@Chi no, it's based on whatever is set in settings.php or \Drupal::VERSION if nothing is set.

Should look something like this.

The Needs Review Queue Bot → tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

This does not mean that the patch needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

I don't think this is necessary with 📌 Remove the aggregate stale file threshold and state entry Fixed so marking duplicate.