Avoid Exception on Glances missing key

[wittypluck]

Proposed change

The aim of this PR is to handle gracefully the case where a Glances sensor is removed server side.
In that case, HA should stop updating this sensor and mark it as Unavailable.
Today, the code breaks (exception in logs).

In more detail, there are three cases where Glances data can become unavailable after the inital setup completes correctly:

1. Request to the server fails, no data available at all => already handled by existing code
2. Configuration changes server side to remove a whole module (eg: fs, network) => currently provokes a missing key error, now handled by this PR to mark sensors as Unavailable
3. Configuration changes server side to remove an item in a module (eg: hide a filesystem in fs module, or hide a network adapter in network module) => currently provokes a missing key error, now handled by this PR to mark sensors as Unavailable

The PR adds systematic checks that the keys used are present in the data provided by python-glances-api. If not, the value is set to None.
It also updates the logic of available() to check for None values.

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: possibly fixes Glances regularly reports KeyError: 'disk_use' #108945
• This PR is related to issue:
• 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.
• 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 @engrbm87, mind taking a look at this pull request as it has been labeled with an integration (glances) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of glances 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 glances Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

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

[wittypluck]

Hello @gjohansson-ST , have you had time to look at my answers to your questions ?
(Not sure if I should mark them as resolved as I haven't made changes to the code)
Thanks !

[wittypluck]

I have also updated the PR description to explain in more detail why this change is useful.

Fine to leave as is

[emontnemery]

@wittypluck OK! I've marked the PR as draft, please click the "Ready for review" button when you've addressed the comment.

[wittypluck]

Thank you! I have rebased, made the change and resubmitted for review.

[gjohansson-ST]

Thanks @wittypluck 👍

[wittypluck]

Thank you @gjohansson-ST and @emontnemery !