fix: server shutdown logging and request context

[Fazt01]

• Canceling Server.Run() context no longer cancels requests base context.

  • because I'd argue there is no usecase where you would want to not-so-gracefully shutdown all running requests. More reasonable use case is to let requests finish (for up to default 30 secs, or before SIGKILL), and if they do not finish, there is nothing too much better that force killing the app

• No Error logging on successful graceful shut down.

  • because it is weird to see error logs when tasks in ECS are swapped as they are supposed to.

• few comments as I was confused what does the hook actually do (RegisterOnShutdown does not wait for hooks to complete, but then there is explicit waiting for those hooks before Run returns)

related: https://github.com/strvcom/backend-go-template-api/pull/166

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 64.24%. Comparing base (28d324b) to head (6a623c9).

Files	Patch %	Lines
http/server.go	50.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #34      +/-   ##
==========================================
+ Coverage   63.95%   64.24%   +0.28%     
==========================================
  Files          12       12              
  Lines         652      646       -6     
==========================================
- Hits          417      415       -2     
+ Misses        223      218       -5     
- Partials       12       13       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.