fix: change vks upgrade logic (#491)

## What ❔

vks should be updated if any vk is update

## Why ❔

contract were changed, changing server as well

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [x] Code has been formatted via `zk fmt` and `zk lint`.

core/lib/types/src/protocol_version.rs

@@ -428,8 +428,8 @@ impl TryFrom<Log> for ProtocolUpgrade {
             default_account_code_hash: (default_account_code_hash != H256::zero())
                 .then_some(default_account_code_hash),
             verifier_params: (recursion_node_level_vk_hash != H256::zero()
-                && recursion_leaf_level_vk_hash != H256::zero()
-                && recursion_circuits_set_vks_hash != H256::zero())
+                || recursion_leaf_level_vk_hash != H256::zero()
+                || recursion_circuits_set_vks_hash != H256::zero())
             .then_some(VerifierParams {
                 recursion_node_level_vk_hash,
                 recursion_leaf_level_vk_hash,