Similar to SERVER-88188 and SERVER-93054, the CheckMetadataConsistency hook should ignore LockBusy errors on ppc64le build variants, as they are considered slow.

The checkMetadataConsistency command, which is sent in the background by the MetadataConsistencyChecker hook, can fail with a LockBusy error when a DDL lock acquisition times out (300 seconds).

If we run the hook in slow build variants, it is expected that some DDL operations will last longer than the timeout for the DDL lock acquisition of the checkMetadataConsistency, making the test fail.

We need to ensure that the ppc64le build variants do not throw an error if the MetadataConsistencyChecker hook fails with a DDL lock busy.