Fix SharkIQ token expiration

[funkybunch]

Proposed change

This update fixes a bug in the SharkIQ integration where tokens are not refreshed after expiring, or are not refreshed ahead of expiring.

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 SharkIQ Integration loses connection frequently; integration must be reloaded daily. #44775 Shark IQ Integration can't be added - Unexpected error #60422
• This PR is related to issue:
• Link to documentation pull request: Documentation update not required.

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

Code owner commands

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

[XBadPlayerX]

Glad you are doing okay!

Thanks for your work.

[funkybunch]

Dependency requirements have been merged to dev - marking as ready for review.

[frenck]

I've marked this PR, as changes are requested that need to be processed above.
Please un-draft it once it is ready for review again by clicking the "Ready for review" button.

Thanks! 👍

../Frenck

Learn more about our pull request process.

[funkybunch]

@Swamp-Ig I took an alternative approach that should negate the need to attempt re-auth in the exception blocks. Hopefully that alleviates your concerns.

[funkybunch]

I've marked this PR, as changes are requested that need to be processed above. Please un-draft it once it is ready for review again by clicking the "Ready for review" button.

@frenck I took an alternative approach that should alleviate the concerns from @Swamp-Ig. I know you all are getting ready for the 2023.4 release tomorrow, but if this looks good to you, I know the community would love to see this bug fix soon. Could it potentially be a candidate for a minor release (2023.4.X)?

[Swamp-Ig]

That's better :)

[frenck]

Thanks, @funkybunch 👍

../Frenck

[frenck]

Oh a merge conflict appeared, could you take a look @funkybunch?

Thanks!

../Frenck

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

[funkybunch]

Oh a merge conflict appeared, could you take a look @funkybunch?

Yup, my guess is it is related to some changes to the tests file that was merged in the other day. I'll have it cleaned up soon.

[funkybunch]

@frenck All set!

[frenck]

Thanks for the quick turnaround @funkybunch 👍

../Frenck