No longer logging connection closed exception when app closes

[WhitWaldo]

Description

No longer passing exception when workflow is shut down per cancellation request. As explained in the linked issue, cancellation is requested when there's an intentional effort to close the connection, not because of something unintended, so it follows that an exception shouldn't be logged on such an intentional behavior. The case was made and I agree.

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #1837

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.46%. Comparing base (c63d7a4) to head (8fff630).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1841   +/-   ##
=======================================
  Coverage   63.46%   63.46%           
=======================================
  Files         312      312           
  Lines        9279     9279           
  Branches     1101     1101           
=======================================
  Hits         5889     5889           
- Misses       3129     3130    +1     
+ Partials      261      260    -1     

Flag	Coverage Δ
net10.0	63.45% <ø> (ø)

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

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.