LU-15985 e2fsck: skip block scanning if the inode is too bad

LU-15985 e2fsck: skip block scanning if the inode is too bad

If the inode is badly corrupted, scanning the extent tree/blocks could
get stuck repeating the error with:
Inode %i block %b conflicts with critical metadata, skipping block checks.

This error PR_1_CRITICAL_METADATA_COLLISION bumps up inode badness by 2
already, we could skip the block/extent scanning if the inode badness is
above the threshold.

Add test case f_ibadness_meta_collision to verify this.

Change-Id: Ifd7246ee8cceb4ea11d2c255310c5af0176bfb1c
Signed-off-by: Li Dongyang <dongyangli@ddn.com>
Reviewed-on: https://review.whamcloud.com/c/tools/e2fsprogs/+/55802
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Li Xi <lixi@ddn.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>