fix(module:notification): don't create new messageId for update

[Nicoss54]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

This PR is a fix for generating a new messageId for updating notification

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

When we update a notification, the service generate a new messageId

Issue Number: 7975

What is the new behavior?

When we update a notification, the service don't generate a new messageId

Does this PR introduce a breaking change?

[ ] Yes
[x] No

[zorro-bot]

This preview will be available after the AzureCI is passed.

[codecov]

Codecov Report

Merging #8000 (a5820ba) into master (605e969) will increase coverage by 91.70%.
The diff coverage is 100.00%.

❗ Current head a5820ba differs from pull request most recent head 6e77b95. Consider uploading reports for the commit 6e77b95 to get more accurate results

@@             Coverage Diff             @@
##           master    #8000       +/-   ##
===========================================
+ Coverage        0   91.70%   +91.70%     
===========================================
  Files           0      514      +514     
  Lines           0    17574    +17574     
  Branches        0     2690     +2690     
===========================================
+ Hits            0    16117    +16117     
- Misses          0     1162     +1162     
- Partials        0      295      +295     

Impacted Files	Coverage Δ
components/message/base.ts	93.44% <100.00%> (ø)
components/notification/notification.service.ts	100.00% <100.00%> (ø)

... and 512 files with indirect coverage changes

[Nicoss54]

@simplejason could you check why the Pipeline is not trigger ? still in the same status Waiting for status to be reported

[Nicoss54]

@simplejason could you check why the Pipeline is not trigger ? still in the same status Waiting for status to be reported

It’s fix ;)

[simplejason]

LGTM