Use ValidateBundlePath for setup command

As of now there is no warning as part of setup if specified bundle
doesn't correspond to the expected one. This patch uses ValidateBundlePath
which validate user's specify bundle patch  and also let user
know if the bundle is in used, different from the expected one.

```
$ ./crc setup -b ~/.crc/cache/crc_libvirt_4.10.22_amd64.crcbundle
WARN Using crc_libvirt_4.10.22_amd64.crcbundle bundle, but crc_libvirt_4.11.0_amd64.crcbundle is expected for this release

$ ./crc config set bundle ~/.crc/cache/crc_libvirt_4.10.22_amd64.crcbundle
WARN Using crc_libvirt_4.10.22_amd64.crcbundle bundle, but crc_libvirt_4.11.0_amd64.crcbundle is expected for this release
Successfully configured bundle to /home/prkumar/.crc/cache/crc_libvirt_4.10.22_amd64.crcbundle
```

cmd/crc/cmd/setup.go

@@ -58,7 +58,7 @@ func runSetup(arguments []string) error {
 	}
 
 	if !config.Get(crcConfig.Bundle).IsDefault {
-		if err := validation.ValidatePath(config.Get(crcConfig.Bundle).AsString()); err != nil {
+		if err := validation.ValidateBundlePath(config.Get(crcConfig.Bundle).AsString(), crcConfig.GetPreset(config)); err != nil {
 			return err
 		}
 	}