[9.0][Search] fix: incorrect docs explorer paging result

[seialkali]

Summary

Fixes incorrect paging info display in the Docs Explorer when an attached index has no documents. Previously, the view showed Showing 1-0 of 0. After updating @elastic/search-ui and related packagesto^1.24.0, the view correctly displays Showing 0-0 of 0`.

Testing

1. Go to search applications
2. Create an application with an index that has no documents
3. Go to the details page for application
4. On the Docs Explorer you should see the correct display for the paging info view: Showing 0-0 of 0

Before

After

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• Flaky Test Runner was used on any tests changed
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

Release note

Fixes an issue in the Docs Explorer where the paging info displayed incorrectly when the attached index had no documents. After updating @elastic/search-ui and related packages to ^1.24.0, the view now shows the correct result count.

[yansavitski]

LGTM

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 744a699

Failed CI Steps

• FTR Configs #62

Test Failures

• [job] [logs] FTR Configs #62 / Space awareness agents POST /agents/bulkUpdateAgentTags should only update tags of agents in the same space when passing a kuery

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
enterpriseSearch	1263	1112	-151

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
enterpriseSearch	1.3MB	1.3MB	+2.3KB
logsExplorer	204.9KB	204.9KB	-4.0B
observabilityOnboarding	251.8KB	251.0KB	-809.0B
total			+1.5KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
enterpriseSearch	38.8KB	39.2KB	+444.0B
kbnUiSharedDeps-npmDll	6.1MB	6.1MB	-12.0B
logsShared	146.0KB	146.0KB	-2.0B
total			+430.0B

History

• 💚 Build #344998 succeeded d561297
• 💔 Build #342715 failed 8dbf5ed
• 💛 Build #336326 was flaky 32a424f