Shield service call from cancellation on REST API connection loss

[Shulyaka]

Breaking change

When calling a service from REST API, the service used to be cancelled on connection drop. If you relied on that behavior, you would need to revisit the logic. With this change, a connection drop will not cancel the service call. Additionally, if the service call takes more than 10 second to execute, the REST API will return and the service call will continue executing in the background. Although this behavior is documented, it was not the case for several past releases.

Proposed change

This PR restores the behavior in the REST API documentation: when a service call is executed via /api/services/<domain>/<service>, the call should return when the service has been executed or after 10 seconds, whichever comes first.
Also, this PR fixes the cancellation of the service call on disconnect.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes Automation is cancelled on API client disconnect #101751
• This PR is related to issue:
• Link to documentation pull request: Not required, the behavior is already documented.

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (api) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of api can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign api Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[bdraco]

please see #102657 (comment)

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[Shulyaka]

The breaking change label should probably be added manually to the PR

stale

[bdraco]

close/reopen to restart ci

[MartinHjelmare]

Thanks!

[bdraco]

Thanks @Shulyaka @MartinHjelmare

[Shulyaka]

Thanks for the review!