fix: validate next boot patch before attempting to boot

[bryanoltman]

Support the changes made in shorebirdtech/updater#297

Accessing next_boot_patch no longer performs validation that the patch is bootable, so we need to call shorebird_validate_next_boot_patch before attempting to boot.

[felangel]

I don't think I have the full context here. I see that we've decoupled getting the next boot patch from validating it but it's not clear to me whether this is solving the 2 validation calls per boot issue and if so how?

[eseidel]

You can push with --no-verify to bypass the checks.

[bryanoltman]

@felangel More context:

Any time the next_boot_patch was accessed, whether for its number, path, or anything else, some basic integrity checks were performed. When booting, this happens through shorebird_next_boot_patch_path. After booting, the updater's patch check logic will ask for the next_boot_patch when determining whether to install the latest available patch (see should_install_patch in updater.rs).

These checks are run more frequently when using package:shorebird_code_push. checkForUpdate calls should_install_patch (which calls next_boot_patch) and then readNextPatch, which also calls next_boot_patch.

[bryanoltman]

You can push with --no-verify to bypass the checks.

Thanks! Done.