fix(chat): Fix responding with "X-Chat-Last-Common-Read" when request…

[nickvergessen]

…ed by the client

☑️ Resolves

Before

    Then last response has last common read message header set to "Message 3"               # FeatureContext::hasChatLastCommonReadHeader()
    When next message request has the following parameters set                              # FeatureContext::setChatParametersForNextRequest()
      | lastCommonReadId   | Message 1 |
      | lastKnownMessageId | Message 3 |
      | timeout            | 0         |
      | lookIntoFuture     | 1         |
    Then user "participant1" sees the following messages in room "chatting" with 200        # FeatureContext::userSeesTheFollowingMessagesInRoom()
      ❌ Failed asserting that 304 matches expected 200.

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included or not required
• 📘 API documentation in docs/ has been updated or is not required
• 📗 User documentation in https://github.com/nextcloud/documentation/tree/master/user_manual/talk has been updated or is not required
• 🔖 Capability is added or not needed

[nickvergessen]

/backport to stable27

[nickvergessen]

/backport to stable26

[backportbot-nextcloud]

The backport to stable26 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable26
git pull origin stable26

# Create the new backport branch
git checkout -b fix/foo-stable26

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable26

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport