Phantom Compute service changes caused by `source_code_hash` discrepancies

## The problem
Issue fastly/terraform-provider-fastly#1160 (closed, 11 comments): ## Overview Last week I noticed that the provider keeps reporting a pending change even though the Compute binary remains unchanged. No matter how many times you apply the change, the result is always identical: ```console Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: ~ update in-place Terraform will perform the following actions: # module.compute.fastly_service_compute.foo will be updated in-place ~ resource "fastly_service_compute" "foo" { ~ active_version = 112 -> (known after apply) ~...

## What fixed it
The phantom diffs came from an upstream hash behavior issue that has since been corrected. Run one apply to update the stored hash; subsequent plans should come back clean.