fix: Update comments post-hotfix (#556)

## What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

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

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

---------

Signed-off-by: Danil <deniallugo@gmail.com>
Co-authored-by: Danil <deniallugo@gmail.com>

core/lib/zksync_core/src/sync_layer/batch_status_updater.rs

@@ -267,9 +267,6 @@ impl BatchStatusUpdater {
     }
 
     /// Inserts the provided status changes into the database.
-    /// This method is not transactional, so it can save only a part of the changes, which is fine:
-    /// after the restart the updater will continue from the last saved state.
-    ///
     /// The status changes are applied to the database by inserting bogus confirmed transactions (with
     /// some fields missing/substituted) only to satisfy API needs; this component doesn't expect the updated
     /// tables to be ever accessed by the `eth_sender` module.

deny.toml

@@ -8,6 +8,7 @@ yanked = "warn"
 notice = "warn"
 ignore = [
     "RUSTSEC-2023-0018",
+    "RUSTSEC-2023-0071"
 ]
 
 [licenses]