Fix adding virtual DSM system in synology_dsm

[mib1185]

Proposed change

This PR fixes an issue where virtual DSM systems can`t be added, because there are nor disks available on vDSM systems.

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)
• 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 Unable to add second Synology DSM instance to HomeAssistant #40209
• 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
• 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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[probot-home-assistant]

Hey there @hacf-fr, @Quentame, mind taking a look at this pull request as its been labeled with an integration (synology_dsm) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[Quentame]

Can you rebase since #42378 has been merged ?

Thanks 😊

[mib1185]

grmmml ... I´m not sure, what is wrong or what happens :/ This git magic is still to new to me 😢
if you have any hints for me, how to solve this and how to perform the rebase properly, I would be very grateful 😃

[Quentame]

Actually you should interactive rebase and keep only the commit of this PR, and drop other commits.

Or easier : rename your branch (add -old) at the end, create a new branch from dev with the same name, and cherry pick the commits of the PR from your -old branch.

Courage 😉

[Quentame]

Please avoid merge.
With that, it integrates commits that are not your own, into the PR.

[mib1185]

ok ... I think I get it now 😃
The previous merge was not on purpose done by me 🙈

[Quentame]

🙏 Thanks for the help on this issue 🤩

[mib1185]

🙏 Thanks for the help on this issue 🤩

you are welcome 😃

[Quentame]

Thanks for your help 👍

Merged !