Lack of visual feedback during publishing actions in Strapi Admin Panel
<!--
Hello 👋 Thank you for submitting an issue.

Before you start, please make sure your issue is understandable and reproducible.
To make your issue readable make sure you use valid Markdown syntax.

https://guides.github.com/features/mastering-markdown/

Please ensure you have also read and understand the contributing guide.

https://github.com/strapi/strapi/blob/main/CONTRIBUTING.md#reporting-an-issue
-->

## Bug report

### Required System information

Node.js version: 18.17.0
YARN version: 1.22
Strapi version: 5.6.0
Database: PostgreSQL
Operating system: Windows
Project language: JavaScript

<!-- Did you know you can run `yarn strapi report` or `npm run strapi report` to get this information easier? -->

### Describe the bug

When performing a "Publish" action in Strapi, the user interface does not provide any feedback indicating that the publishing process is in progress. There is no spinner, progress bar, or message displayed. This creates confusion and may lead users to click the "Publish" button multiple times, resulting in errors such as "duplicate key value violates unique constraint" when duplicate submissions occur.

### Steps to reproduce the behavior

1. Log in to the Strapi admin panel.
2. Navigate to a collection type you created.
3. Edit an existing entry or create a new one.
4. Click the "Publish" button.
5. Observe the lack of any visual feedback or indication that the publish process is occurring.


### Expected behavior

The UI should provide clear and immediate feedback when the "Publish" button is clicked, such as:

A spinner or loading icon near the button.
A message indicating "Publishing in progress..."
Confirmation of successful publishing once the process is complete.
This would enhance the user experience and prevent unintended duplicate actions.

### Screenshots

![image](https://github.com/user-attachments/assets/e169d268-eefb-450d-abe8-e03a5347115a)

### Code snippets

Not applicable 

### Additional context

This issue impacts user experience, especially in environments where publishing actions take time. Without feedback, users may think the action did not initiate and attempt multiple submissions. This can result in database errors, as seen with the "duplicate key value violates unique constraint" error during publishing.
