Need to fix super bytes mismatch & scrub in one run

[tribbloid]

Here is a case where the file system is in a state of inconcistency:

$ sudo btrfs check --repair --check-data-csum /dev/nvme0n1p7
enabling repair mode
WARNING:

	Do not use --repair unless you are advised to do so by a developer
	or an experienced user, and then only after having accepted that no
	fsck can successfully repair all types of filesystem corruption. E.g.
	some software or hardware bugs can fatally damage a volume.
	The operation will start in 10 seconds.
	Use Ctrl-C to stop it.
10 9 8 7 6 5 4 3 2 1
Starting repair.
Opening filesystem to check...
Checking filesystem on /dev/nvme0n1p7
UUID: a5c81116-78a5-4edb-b57c-b08e90e1391b
[1/7] checking root items
Fixed 0 roots.
[2/7] checking extents
super bytes used 439853678592 mismatches actual used 439853662208
super bytes used 439853694976 mismatches actual used 439853678592
No device size related problem found
[3/7] checking free space tree
[4/7] checking fs roots
[5/7] checking csums against data
mirror 1 bytenr 12203282432 csum 0x76d31b90 expected csum 0x7d230f0e
mirror 1 bytenr 25842708480 csum 0x02e5c95a expected csum 0xddce973b
mirror 1 bytenr 25842712576 csum 0x8800cbba expected csum 0x9eb53475
mirror 1 bytenr 25842716672 csum 0x12936a8a expected csum 0x8c252ad4
mirror 1 bytenr 25842720768 csum 0x7cc7608c expected csum 0x757f178f
mirror 1 bytenr 25842724864 csum 0x6e3cae93 expected csum 0x410de030
mirror 1 bytenr 25842728960 csum 0xd33e2dc2 expected csum 0x020b5e4b
mirror 1 bytenr 25842733056 csum 0x2b9dd46e expected csum 0xa1eab685
mirror 1 bytenr 25842737152 csum 0x15ae996d expected csum 0xe4e6138d
mirror 1 bytenr 25842741248 csum 0x993f3c77 expected csum 0xb62ee535
mirror 1 bytenr 25842745344 csum 0xe88710df expected csum 0xa07ad4e2
ERROR: errors found in csum tree
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 1319561035776 bytes used, error(s) found
total csum bytes: 228758556
total tree bytes: 8702115840
total fs tree bytes: 7584399360
total extent tree bytes: 785989632
btree space waste bytes: 1913237028
file data blocks allocated: 1515374493696
 referenced 1330351448064

it has at least 2 types of error: super bytes mismatch and csum mismatch. the command fail to fix any of them

traditionally, the csum mismatch can be fixed by either scrubbing (fast) or rebuilding the csum tree (slow), unfortunately, we don't have a routine to try both automatically.

can we add an option to first try to scrub, and if it fails, rebuild the csum tree?