Investigate whether we need fsck in CentOS Automotive images

On fast hardware we spend 30ms each fscking /boot and /root ext4 partitions. On common Automotive hardware, this probably translates to around ~100ms.

```
systemd-analyze plot | grep -i fsck
system-systemd\x2dfsck.slice
systemd-fsck-root.service (33ms)
systemd-fsck@dev-disk-by\x2duuid-156f0420\x2d627b\x2d4151\x2dae6f\x2dfda298097515.service (29ms)
```

note we plan on using composefs also, which can detect some bad data.

We should see what fsck is doing exactly during boot time here on ext4 partitions and see if it's worth the extra milliseconds it adds to boot.