[KS-602] Fix for remote executable client not respecting context

[bolekk]

When context is cancelled (e.g. on Engine instance shutdown), ClientRequest will shut down all pending sender goroutines with a log "context done, not sending request to peer" but it won't send anything back on the response channel. That will happen only much later, when a request expires (via expireRequests()).

Two solutions I considered:
(1) [IMPLEMENTED] Wait on the response channel together with the context.
(2) [ALTERNATIVE] Guarantee that ClientRequest always sends something back. Seems to be more error-prone and also a bit awkward to implement.

[github-actions]

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[github-actions]

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit