improve notification toast when saving a file #9803

[rdsingh13]

Closes #9803

I commented Saving library because its take no time in saving library so only one notification came Library saved

Mandatory checks

• Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (for UI changes)
• Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
• Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

[calixtus]

Hi, thanks for your interest in jabref and open source programming.
Is there any issue linked to this pr you are fixing? Could you elaborate a bit on this description, whats the reasoning for your change?

[calixtus]

Just saw the PR title.
Please note that GitHub does not parse pr titles, only the description of your pr. So if you automatically want to link your pr to an issue, you have to write fixes or closes followed by the issue number in the description. Like this:
Closes #9803

[calixtus]

After reading through your changes and the issue description:
If you want to remove code, remove it, not just comment it. To keep a history of code changes is what git is for.
Secondly, the issue comments indicated, that there has not been yet a decision made on how to deal with the notifications. I will put a dev call tag on this one therefor.

[Siedlerchr]

Do not remove this. for lage libraries it will take some time