update test data of CarpetProlongateTest

[Roland Haas]

commit 4acaa0d0d3e59d6e618815515871f1f1115a6789 to Carpet removed an automated sync call. Since the tests do not behave like user thorns would (ie they do not schedule boundary calls after restriction since they want to verify restriction) their results changed.

The attached patches regenerate data that changed. Generically the changes seem to be more zeros in the "difference" variables.

Keyword:

[Roland Haas]

Applied as hash b3bc3f55da065426329f806ea9b26538bb6e4ee1 "CarpetProlongateTest: update test data"