Deprecate the dynamic package sensors in seventeentrack

[shaiu]

Breaking changes

...

Proposed change

Add deprecation comments for the dynamic package sensors

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 #
• 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][dev-checklist]
• I have followed the [perfect PR recommendations][perfect-pr]
• 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][docs-repository]

If the code communicates with devices, web services, or third-party tools:

• The [manifest file][manifest-docs] 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][prs] in this repository.

[davet2001]

Since the beta for 2024.5 has now been cut, the earliest deprecation start will be 2024.6.

Also is it possible to raise a deprecation warning when the deprecated functions are used?

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

[shaiu]

@joostlek what did we decide on here?

[joostlek]

I think there are 2 things we should keep in mind after I did some reviewing of the code

1. Can we get all data from the service call that was previously in the state attributes? I think we are missing the information from the individual package sensors
2. We will probably have an options field with like "create individual package sensors" that will be fixed by a repair flow. So whenever you start the integration after this is merged, a repair issue will be raised, asking you to migrate to the service calls. If you press the submit button, the options to create those sensors will turn off and then those people are migrated.

I think it would also be nice to have some example templates in the documentation to help people get started with this new way of fetching the extra data. I can ask some people if they are able to help out with this.