Disable AVM FRITZ!Box Tools device_tracker entities by default

[mib1185]

Breaking change

Since in most cases the amount of really wanted to be tracked devices is quite lower than the overall count of devices, device_tracker entities will be disabled by default and the user needs to enable wanted device_trackers, even newly detected devices.

Proposed change

After discussions starting from #50574 (comment) device_trackers from platform fritz will be disabled by default, since in most cases the amount of really wanted to be tracked devices is quite lower than the overall count of devices.

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 #
• 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 @mammuth, @AaronDavidSchneider, @chemelli74, mind taking a look at this pull request as its been labeled with an integration (fritz) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[tschamm]

Looks fine for me and shows the expected behavior during initialization.

I wonder if disable_new_entities property should be added as well? To my understanding new entities of the same config entry are otherwise added by default.

[mib1185]

I would keep disable_new_entities as is, since new device_tracker entities will still be added, but still disabled based on entity_registry_enabled_default

[tschamm]

Thanks for your explanation. Ok from my side.

[tschamm]

Why is this a breaking change? Your changes will only affect entities which are newly registered. Users who already loaded the integration will not see a changed behavior.

[mib1185]

Yeah, honestly I struggled a bit with my self, if it is a breaking change or not, but in case a new devices is detected by Fritzbox, currently it will be added as enabled device_tracker , after this PR it will be still added, but disabled.

EDIT: I've extended the breaking change note, to make it more clear

[janiversen]

When an integration changes behavior it is good to state it as a breaking change, even though many will no5 be affected.

The edit made it more understandable

[MartinHjelmare]

Thanks!