Upgrade Prusa Link to new Digest Authentication and /v1/ API

[Skaronator]

Breaking change

• printer.state now contains several new statuses, most importantly "attention" which always needs user invention
• Firmware 4.7.0 is now the minimum version for Prusa XL and MK4
• Firmware 5.1.0 is now the minimum version for Prusa Mini since 4.7.x and 5.0.x aren't available for the Mini

Proposed change

This PR updates pyprusalink library.

• home-assistant-libs/pyprusalink@1.1.0...2.0.0
• The library now uses /v1/ API endpoints for most request.
• Additionally, it switched from API Key Auth to HTTP Digest Auth since API Key auth is deprecated.

Tested with my XL on 5.1 firmware

New Attention Status:

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 relies on: Switch to v1 API endpoints and use DigestAuth home-assistant-libs/pyprusalink#63
• Link to documentation pull request: Upgrade Prusa Link to new /v1/ API home-assistant.io#29699

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 @balloob, mind taking a look at this pull request as it has been labeled with an integration (prusalink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of prusalink 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 prusalink Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[rforro]

From config_flow.py following code needs to be removed or modified, because PrusaLink for RaspberryPi uses V1 as well, but advertise api version as 0.9.0-legacy.

try:
        if AwesomeVersion(version["api"]) < AwesomeVersion("2.0.0"):
            raise NotSupported

The Prusa api versioning is a bit mess they advertise different numbers on MINI/MK4/XL/PrusaLink(RaspberryPi), thats why checking api value is bad.

EDIT: After some digging I think, that buddy FW MINI/MK3.5/MK4 will report 2.0.0 everytime. It doesn't matter if they support V1 or not. So the version problem is only PrusaLink for RaspberryPi. Maybe they just forget to set it to 2.0.0. I will clarify this.

[edenhaus]

Please make sure CI is passing

[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.

[edenhaus]

• printer.telemetry.material is no longer available. The new API doesn't is currently far too slow to fetch this information. Additionally, the current implementation is broken for multi material prints.

Would it be possible to use the old API for this endpoint? So we can avoid the breaking change?

[Skaronator]

@rforro I would leave that version condition as it is unless anyone who owns an MK3x with a Raspberry Pi running Prusa Link wants to contribute. But that change can happen in a future PR.

@edenhaus I'll look into it.

[Skaronator]

I've re-added the Material sensor using the old API. So the only breaking change is now the Enum in the printer.state sensor.

[Skaronator]

Implemented all review suggestions. Thanks @edenhaus!

[edenhaus]

Thanks @Skaronator 👍

[edenhaus]

Test failure unrelated:
FAILED tests/helpers/test_script.py::test_wait_template_with_utcnow - Failed: Timeout >9.0s

[Skaronator]

Awesome thanks for the review!