fix: different no transaction messages for non-existing and empty batches/blocks

[vasyl-ivanchuk]

What ❔

Different no transaction messages for non-existing and empty batches/blocks: Empty batch:

Non-existing batch:

Why ❔

For better UX we want to show different no transaction messages in different cases: This Batch doesn’t have any transactions - for empty batch, This Batch has not been created or sealed yet - for non-existing batch, same for blocks.

Checklist

• [X] PR title corresponds to the body of PR (we generate changelog entries from PRs).
• [X] Tests for the changes have been added / updated.

[github-actions[bot]]

API E2E Test Results

206 tests   206 :heavy_check_mark:  28s :stopwatch:   14 suites      0 :zzz:     1 files        0 :x:

Results for commit 16444f54.

[github-actions[bot]]

Visit the preview URL for this PR (updated for commit 16444f5):

• https://staging-scan-v2--pr107-add-new-text-for-zer-s96bywum.web.app
• https://staging-storybook-scan-v2--pr107-add-new-text-for-zer-g3umeoam.web.app

_{(expires Mon, 11 Dec 2023 05:52:50 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: e508f9012944951194447cb8885950b451a24403}

[github-actions[bot]]

Unit Test Results

       3 files     246 suites   8m 26s :stopwatch: 1 938 tests 1 937 :heavy_check_mark: 1 :zzz: 0 :x: 1 964 runs  1 963 :heavy_check_mark: 1 :zzz: 0 :x:

Results for commit 16444f54.

[github-actions[bot]]

:tada: This PR is included in version 2.31.3 :tada:

The release is available on:

• v2.31.3
• v2.31.3
• v2.31.3
• GitHub release

Your semantic-release bot :package::rocket: