Docker build cache invalidation is too aggressive

Docker layer caching is supposed to speed up builds, but cache invalidation is far too aggressive. Changing a comment in a Dockerfile invalidates all subsequent layers, even when the actual build instructions haven't changed. This wastes enormous CI time and bandwidth. This has been a known issue for years and the BuildKit improvements haven't fully addressed it.