Unnecessary asset optimization for old aggregated URLs

Problem/Motivation

After #3454507: Aggregated asset generation causes uncacheable assets we don't need to optimize assets when the hash from URL doesn't match.

Steps to reproduce

Proposed resolution

Optimize only if the hash matches.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet