[notifications] Give each HTTP request its own context

[S7evinK]

Give each HTTP request its own context to avoid timing out subsequent notification requests if the first already times out.

Pull Request Checklist

• I have added Go unit tests or Complement integration tests for this PR or I have justified why this PR doesn't need tests
• Pull request includes a sign off below or I have already signed off privately

[CLAassistant]

All committers have signed the CLA.

[Copilot]

Pull Request Overview

This PR aims to give each HTTP request its own context to prevent one slow or timed-out notification from affecting subsequent requests. Key changes include:

• Increasing the outer context timeout from 30 seconds to 5 minutes.
• Creating individual HTTP contexts with a 30-second timeout for each HTTP notification request.

Comments suppressed due to low confidence (2)

userapi/consumers/roomserver.go:609

• [nitpick] Consider verifying that the extended global context timeout of 5 minutes is appropriate for all scenarios, ensuring that resources are not held longer than necessary while still providing sufficient time for individual HTTP requests.

ctx, cancel := context.WithTimeout(context.Background(), 5*time.Minute)

userapi/consumers/roomserver.go:627

• [nitpick] Ensure that invoking httpCancel immediately after the HTTP request call consistently cleans up the context, especially if s.notifyHTTP has any asynchronous behavior.

httpCtx, httpCancel := context.WithTimeout(ctx, 30*time.Second)