fix(react): update lastMessageUpdate consistently with Webchat Settings

[vanbasten17]

Description

• Update logic to be consistent when resending WebchatSettings.

Linked PR: https://github.com/metis-ai/hubtype-backend/pull/552

[asastre]

Since WebchatSettings is not a message by itself I don't know if it make sense to update the last message date. What do you think?

[vanbasten17]

@asastre it's true that is not a message itself, but when resending unread messages from backend, the last message update date should be taken into account in order to not send additional WebchatSettings messages.

[codecov]

Codecov Report

Merging #1355 (c88fbe1) into master (8581b75) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1355      +/-   ##
==========================================
- Coverage   63.20%   63.19%   -0.01%     
==========================================
  Files         252      252              
  Lines        7075     7076       +1     
  Branches     1182     1182              
==========================================
  Hits         4472     4472              
- Misses       2261     2262       +1     
  Partials      342      342              

Flag	Coverage Δ
botonic-react	57.57% <0.00%> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
packages/botonic-react/src/webchat/webchat.jsx	47.70% <0.00%> (-0.15%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8581b75...c88fbe1. Read the comment docs.

[vanbasten17]

@asastre , you were right, there is no need to update the lastMessageDate. When doing the auth call, last message id will be the previous one just before the WebchatSettings in DB. So I'm closing this PR atm. It's a backend issue.