Fix rainforest_raven closing device due to timeout

[cottsay]

Proposed change

When there's a timeout initializing the device, it's possible that a problem with the serial port is blocking the write operations, meaning that the flush() that's part of the call to close() might block. The device is already in a bad state, so we should just use abort() to abandon the attempt so that we can try again. This will close the device without flushing the write buffer.

I'm still not able to reproduce the reported problems with rainforest_raven at startup, but at least one of the backtraces I saw indicated that the call to await device.close() wasn't completing and eventually timed out. Though this change doesn't address why the device timed out to begin with, I'm hoping it mitigates the effects and allows Home Assistant to continue startup and try to open the device again later.

The abort() method was introduced in aioraven 0.7.0, which this PR updates to:
Upstream diff: https://github.com/cottsay/aioraven/compare/0.6.0..0.7.0
Upstream changelog: https://github.com/cottsay/aioraven/blob/0.7.0/CHANGELOG.md#070-2024-07-12

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 #
• This PR is related to issue:
  • Home Assistant boot process gets stuck while loading Rainforest RAVEn integration. #113473
  • RainForest RAVen failed to set up #121811
• Link to documentation pull request:

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 Ruff (ruff format 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.

To help with the load of incoming pull requests:

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

[frenck]

Thanks, @cottsay 👍

../Frenck