chore: improve logging for DA dispatcher and avail client (#4545)

## What ❔

Improve logging for DA dispatcher and Avail client

## Why ❔

For easier debugging in case of any issues in the future.

## Is this a breaking change?
- [ ] Yes
- [ ] No

## Operational changes
<!-- Any config changes? Any new flags? Any changes to any scripts? -->
<!-- Please add anything that non-Matter Labs entities running their own
ZK Chain may need to know -->

## 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 `zkstack dev fmt` and `zkstack dev
lint`.

Author: dimazhornyk

core/node/da_clients/src/avail/client.rs

@@ -293,6 +293,7 @@ impl DataAvailabilityClient for AvailClient {
                 error: anyhow!("Unable to join to URL"),
                 is_retriable: false,
             })?;
+        tracing::debug!("Fetching inclusion data from Bridge API: {}", url);
 
         let response = self
             .api_client
@@ -302,6 +303,11 @@ impl DataAvailabilityClient for AvailClient {
             .await
             .map_err(to_retriable_da_error)?;
 
+        tracing::debug!(
+            "Bridge API HTTP Response size: {:?}",
+            response.content_length()
+        );
+
         // 404 means that the blob is not included in the bridge yet
         if response.status() == StatusCode::NOT_FOUND {
             return Ok(None);

core/node/da_dispatcher/src/da_dispatcher.rs

@@ -291,6 +291,7 @@ impl DataAvailabilityDispatcher {
             return Ok(());
         };
 
+        tracing::debug!("Getting inclusion data for blob_info: {:?}...", blob_info);
         let inclusion_data = if self.config.use_dummy_inclusion_data {
             Some(InclusionData { data: vec![] })
         } else {